Mailing List Archive

route-filter prefix-length-range on inet6 prefixes
Is it possible to use route-filter prefix-length-range to make policy
decisions on inet6 routes? I can input the configuration in edit mode,
however a `commit check` results in the following error:

root@router# show
from {
family inet6;
route-filter 0:0:0:0::0/128 prefix-length-range /16-/32;
}
then accept;

[edit policy-options policy-statement foo term length6]
root@router# commit check
[edit policy-options policy-statement foo term length6 from]
'route-filter 0:0:0:0::0/128 route-filter /16-/32'
Policy: invalid minimum prefix length /16
error: configuration check-out failed

Note that the syntax checker's output is "route-filter <addr6>
route-filter", NOT "route-filter <addr6> prefix-length-range". I see
this behavior on JunOS 6.1R1.4, 6.1R2.2, and 6.2R1.5.

--
Jeff at Reflected Networks
route-filter prefix-length-range on inet6 prefixes [ In reply to ]
On Fri, Feb 13, 2004 at 04:20:57AM -0500, Jeff Wheeler wrote:
> root@router# show
> from {
> family inet6;
> route-filter 0:0:0:0::0/128 prefix-length-range /16-/32;
> }
> then accept;
>
> [edit policy-options policy-statement foo term length6]
> root@router# commit check
> [edit policy-options policy-statement foo term length6 from]
> 'route-filter 0:0:0:0::0/128 route-filter /16-/32'
> Policy: invalid minimum prefix length /16
> error: configuration check-out failed

Your /128 is wrong. Correct:

root# show
from {
family inet6;
route-filter ::0/0 prefix-length-range /16-/32;
}
then accept;

[edit policy-options policy-statement foo]
root# commit check
configuration check succeeds

> Note that the syntax checker's output is "route-filter <addr6>
> route-filter", NOT "route-filter <addr6> prefix-length-range". I see
> this behavior on JunOS 6.1R1.4, 6.1R2.2, and 6.2R1.5.

This looks indeed like a bug.


Regards,
Daniel
route-filter prefix-length-range on inet6 prefixes [ In reply to ]
On Fri, 2004-02-13 at 06:48, Daniel Roesen wrote:
> On Fri, Feb 13, 2004 at 04:20:57AM -0500, Jeff Wheeler wrote:
> > route-filter 0:0:0:0::0/128 prefix-length-range /16-/32;
> Your /128 is wrong. Correct:

Whoops, looks like I burned a bit too much midnight oil! The syntax
checker's output is incorrect, though, which lead me to believe I was
encountering a software problem.

--
Jeff at Reflected Networks