[Xorp-hackers] [Xorp-users] Policy network4 operator

Kristian Larsson kristian at spritelink.se
Sat Nov 18 01:35:43 PST 2006


On Fri, Nov 17, 2006 at 01:46:29PM -0800, Pavlin Radoslavov wrote:
> Kristian Larsson <kristian at spritelink.se> wrote:
> 
> > On Fri, Nov 17, 2006 at 01:34:11PM +0200, Hasso Tepper wrote:
> > > Pavlin Radoslavov wrote:
> > > > "network4 shorter 10.0.0.0/8"   SAME AS "network4 > 10.0.0.0/8"
> > > > "network4 orshorter 10.0.0.0/8" SAME AS "network4 >= 10.0.0.0/8"
> > > 
> > > [snip]
> > > 
> > > > Note that the last three keywords (shorter/orshorter/not) don't
> > > > exist in Juniper, so feel free to suggest better names.
> > > 
> > > What networks you'd expect to match these conditions? Ok, 10.0.0.0/8 would 
> > > match "orshorter" but point being ... ?
> > I've been wondering over the same thing
> > 
> > Would the following expressions do the same thing?
> > cisco:
> > ip prefix-list standard FOO deny 10.0.0.0/8 le 32
> > ip prefix-list standard FOO permit 0.0.0.0/0
> > 
> > xorp:
> > network-list BAR {
> > 	permit orshorter 10.0.0.0/8;
> > }
> 
> I believe the answer is no, because the second Cisco rule will
> permit only the default route 0.0.0.0/0 (please correct me if my
> limited knowledge of Cisco commands is wrong here).
You are correct, however 0.0.0.0/0 le 32 was what
I meant.
Nevertheless, I understand what shorter does now.. :)


> The equivalent XORP-like rule (which BTW is not valid configuration)
> will match the following routes:
> 10.0.0.0/8, 10.0.0.0/7, 8.0.0.0/6, 8.0.0.0/5, 0.0.0.0/4, 0.0.0.0/3,
> 0.0.0.0/2, 0.0.0.0/1, 0.0.0.0/0.
Think of it as XORP pseudo code ;)
I'm not as used to XORP so I can't write config from
heart.

  Kristian.

-- 
Kristian Larsson                                   KLL-RIPE
Network Engineer                      Net at Once [AS35706]
+46 704 910401			     kristian at spritelink.se



More information about the Xorp-hackers mailing list