From: Jongsoo.Kim@Intelsat.com
Date: Mon Feb 07 2005 - 15:36:09 GMT-3
Tim
Here is my answer as I am studying Ipv6 as well.
I think ipv6 address fec0:157:1:14::/64 = ipv6 address fec0:157:1:14::0/64
SO if you <CR>, then fec0:157:1:14::0/64 is your IPV6 site local address.
EUI-64 is based on 24 bits of MAC address + FFFE + 24bit of Mac ADDRESS.
So if MAC is 0000.0C0A.2C51, then EUI is 0000.0C + FF.FE + 0A.2C51.
Final IPv6 address will be fec0:157:1:14:0000:0CFF:FE0A:2C51
Link local address is very important when Ipv6 routing protocol is running.
It is better to manually configure because it's easy to remember.
For example, if you running IPv6 OSPF over frame-relay and you have to
configure frame-relay map,
you must configure something like " frame-realy map ipv6 link-local-address
DLCI broadcast".
In this case, you want to use very easy link-local address such as "FE80::1"
Regards
Jongsoo
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Monday, 07 February, 2005 8: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