[j-nsp] Connected Networks in a prefix list?
Paul Goyette
pgoyette at juniper.net
Thu May 27 09:56:29 EDT 2004
Niels,
Here's an example configuration:
[edit]
lab at frigid# show policy-options
prefix-list direct {
apply-path "interfaces <*> unit <*> family inet address <*>";
}
[edit]
lab at frigid# show interfaces fe-0/0/3
unit 0 {
family inet {
address 20.127.216.2/24;
}
family mpls;
}
And here's what it expands to:
lab at frigid> show configuration | display inheritance | find prefix
prefix-list direct {
##
## apply-path was expanded to:
## 20.127.216.0/24;
##
apply-path "interfaces <*> unit <*> family inet address <*>";
}
Note that the "host bits" have been removed.
-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Niels Bakker
Sent: Thursday, May 27, 2004 6:36 AM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Connected Networks in a prefix list?
Phil,
* phil at juniper.net (Phil Shafer) [Thu 27 May 2004, 15:09 CEST]:
> Niels Bakker writes:
>>Can you reference that prefix-list in a firewall entry? (I can't, even
>>though "commit check" succeeds, a "commit" bails with a checkout error.)
> Can you send me the config this failed on? I couldn't make anything
> that passed "commit check" but failed "commit". All the tests for
> "commit check" are part of a normal commit, so if you're seeing this,
> it's a bug.
I was very probably mistaken when I wrote the above regarding "commit
check". About JunOS's inability to ignore any host bits set, my comment
still holds - looking forward to see what you've done to work around
this in 6.4.
Regards,
-- Niels.
--
Today's subliminal thought is:
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list