From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Mon Feb 07 2005 - 14:47:49 GMT-3
Tim,
How does IPv6 work for L3 to L2 resolution?
And, if routers only have a fixed number of predefined L2 addresses
available to them to pick from, what happens if two adjacent router pick
the same L2 address from the pool especially possible when it comes to
things like serial interfaces.
Once you look at this, then you will know why you might want to hard
code the link-local address. 8)
Something else interesting to note, that because of the way IPv6 works
for L2 to L3 resolution, neat things start to become possible, like
pinging from one IPv6 address to another IPv6 address on the same
physical segment but on different subnets without requiring a router in
between like IPv4.
Look at the IPv6 ICMP usage.
HTH,
andys
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Monday, February 07, 2005 5:21 AM
To: Group Study
Subject: ipv6 eui-64 and link-local
HI guys,
I'm very unclear about when I need to use the eui-64 or link-local
options when configuring an ipv6 address.
For example, what's the difference between the following 2 options?
Rack1R1(config-if)#ipv6 address fec0:157:1:14::/64 ?
eui-64 Use eui-64 interface identifier
<cr>
If I just hit enter <cr>, what will be the value of the low 64 bit's?
Also, regarding the link local option, I understand that ipv6 will
automatically generate a link-local address from the site local or the
aggregatable global unicast address. So, why would I ever want to
override the auto generated link-local address?
Thanks for your help. I'm really struggling with this ipv6 stuff.
Tim
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:17 GMT-3