From: ccie2be (ccie2be@nyc.rr.com)
Date: Wed Jun 08 2005 - 11:50:13 GMT-3
Scott,
Thank you. Slowing the light begins to shine.
Now, based on what you said about discovered neighbors, is this route table
telling me I have a problem?
R4 has 2 ipv6 neighbors: 1 neighbor is on subnet 2001:144:3:46::/64
connected to E0/0 but this neighbor isn't shown.
The another neighbor is via s0/0.24 (p2p) on subnet 2001:144:3:24::/64 but
this neighbor isn't listed either.
Yet, I know R4 is talking RIPng to R2 because R2 is configured to advertise
a default route and that is listed in the ipv6 route table.
R ::/0 [120/2]
via FE80::2D0:BAFF:FE7B:F580, Serial0/0.24
R2 s0/1.24 ------ s0/0.24 R4 e0/0 ------ e0 R6
TIA, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Wednesday, June 08, 2005 10:10 AM
To: 'ccie2be'; 'Group Study'
Subject: RE: Understanding the ipv6 route table
Your own local ID's are listed in there (the /128 is IPv6 equivalent of
/32). Remember that with the EUI-64 thing, not often do people really know
what their own IPv6 addresses are. It's not like a .1, .2, etc any longer.
The FE80::/10 is the entire local-link range. Any learned neighbors
(discovered) will be shown as a more specific route. Anything else unknown
is automatically shipped out to Null0 in order to speed up processing.
Either I know about it or I don't!
FF00::/8 is the multicast range. Again, don't know it, don't use it.
Remember that just like in IPv4 stuff, more specific routes will be used all
the time. These are just to speed up the general thinking process of the
routers and let you (the unsuspecting administrator!) know what's going on.
If you use the "show ip route | don't tell me too much" parameter, the table
will be much more readable!
;)
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Wednesday, June 08, 2005 10:01 AM
To: Group Study
Subject: Understanding the ipv6 route table
Hi guys,
This is a copy of the ipv6 route table from 1 of my routers. I need some
help interpreting what's it's telling me.
When I look at the "L" entries, it seems that they correspond to the
preceding "C" entries except that they include the interface-id until I look
at the last 2 "L" entries.
What are these last 2 entries telling me and why are they there?
TIA, Tim
R4#sh ipv route
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
R ::/0 [120/2]
via FE80::2D0:BAFF:FE7B:F580, Serial0/0.24
C 2001:144:3:24::/64 [0/0]
via ::, Serial0/0.24
L 2001:144:3:24:203:6BFF:FE21:9700/128 [0/0]
via ::, Serial0/0.24
C 2001:144:3:46::/64 [0/0]
via ::, Ethernet0/0
L 2001:144:3:46:203:6BFF:FE21:9700/128 [0/0]
via ::, Ethernet0/0
L FE80::/10 [0/0] <- What's this for ?
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0 <- What's this for?
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3