[j-nsp] Bizarre commit error

[Jared Mauch]

On Sat, Nov 05, 2005 at 09:59:07AM -0500, Eric Van Tol wrote:
> Okay, here's a bizarre one.  Using 7.0R2.7.  Weird commit error while attempting to call a prefix-list from within a policy-statement:
> 
> [edit policy-options]
>   'prefix-list mlppp-local'
>     Policy: invalid prefix Ñ·Âiÿÿÿÿc½¿¿ for family unspec
> [edit policy-options]
>   'prefix-list mlppp-local'
>     Policy: invalid prefix ϼٍÿÿÿÿc½¿¿ for family unspec
> [edit policy-options]
>   'prefix-list mlppp-local'
>     Policy: invalid prefix ϼØÿÿÿÿb½¿¿ for family unspec
> [edit policy-options]
>   'prefix-list mlppp-local'
>     Policy: invalid prefix ϼڵÿÿÿÿc½¿¿ for family unspec
> error: configuration check-out failed
> 
> Error doesn't occur until the prefix-list is called from a routing policy.
> 
> user at router# show policy-options prefix-list mlppp-local | display inheritance     
> ##
> ## apply-path was expanded to:
> ##     192.168.1.1/32; 
> ##     192.168.1.5/32; 
> ##     192.168.1.9/32; 
> ##     192.168.1.13/32; 
> ##
> apply-path "interfaces ls-0/3/0 unit <*> family inet address <*>";
> 
> user at router# show policy-options policy-statement ospf-filter
> 
> term 0-mlppp_routes {
>     from {
>         prefix-list mlppp-local;
>     }
>     then accept;
> }
> 
> Bug?  Operator error?

	Looks like a bug to me, most likely some bad pointer math
or uninitalized memory.  I'm guessing if their devel/regression host
malloc options was set to X it would actually dump core at that
point.

	- jared

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.