From: Scott Morris (swm@emanon.com)
Date: Thu Aug 18 2005 - 08:22:08 GMT-3
Answering your own question is always fun! :)
You can still do passive-interface. It works like ISIS does. Enabling the
protocol on the interface brings the route into the RIB and also activates
it on the interface. A passive-interface command in the global routing
protocol will now simply advertise the route. The protocol will not be
activated on that interface.
RIPng and OSPFv3 were both striving to be ISIS-like in this respect!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Rohan Grover (rohang)
Sent: Thursday, August 18, 2005 3:24 AM
To: ccielab@groupstudy.com
Subject: RE: IPv6 Rip Distribute list
I got the problem, hate it when this happens! I send a mail to groupstudy
and 5 mins later I figure out my brain had stopped working.
:-(
The prefix list is wrong. It should be
ipv6 prefix-list ROHAN seq 5 deny 3001:5::/64
ipv6 prefix-list ROHAN seq 10 permit ::/0 le 128
On a related note...since in IPv6 routing protocols are configured directly
under interfaces, the concept of passive interfaces no longer exists right?
So if I want to advertise a loopback ipv6 int in RIPv6, I would configure
'ipv6 router rip <name>' under Loopback and things work great, but then rip
updates will be sent out on L0 going to Null..this is not really desirable
right? Anything to prevent this?
Thanks
Rohan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Rohan Grover (rohang)
Sent: Thursday, August 18, 2005 12:40 PM
To: ccielab@groupstudy.com
Subject: IPv6 Rip Distribute list
Hi,
I have configured IPv6 RIP on 2 routers R1 and R2. I now want to filter a
certain prefix 3001:5::/64 and permit all others on R2.
To do this I created a ipv6 prefix list on R2
ipv6 prefix-list ROHAN seq 5 deny 3001:5::/64
ipv6 prefix-list ROHAN seq 10 permit ::/0
I applied this list to the ipv6 router rip
ipv6 router rip RIPA
distribute-list prefix-list ROHAN in
But I see that only a default route ::/0 sent by R1 is being installed in
the R2 ipv6 routing table. Other prefixes being advertised by R1 like
2001:1::/64, 2001:2::/64 are all being rejected by the filer as per the
debugs
00:35:14: RIPng: Input filter rejects 2001:1::/64
00:35:14: RIPng: Input filter rejects 2001:2::/64
Why is this happening? Is there a different logic to be used for distribute
list filtering for ipv6?
Any help will be much appreciated.
Thanks
Rohan
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3