From: Scott Morris (smorris@internetworkexpert.com)
Date: Thu Sep 04 2008 - 10:28:11 ART
Because locally generated packets are always sourced from the link-local
address on every interface.
That's why, when you run RIPng or OSPFv3, you'll see the FE80::x addreses as
the next hop in your routing table.
HTH,
Scott Morris, CCIE4 #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
Senior CCIE Instructor
smorris@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344
Online Community: I E O C
CCIE Blog: Nice stuff @ blog . Ourownwebsite . com
Knowledge is power.
Power corrupts.
Study hard and be Eeeeviiiil......
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Mark
Stephanus Chandra
Sent: Thursday, September 04, 2008 9:17 AM
To: 'Cisco certification'
Subject: Link-Local Address on IPv6
Guys,
I still cannot undersand what the main purpose of link-local address. I know
that this addresses just for a link address and cannot be routed.
But when we implement RipNG on frame-relay, if I do not map my link-local
address, the RIP can is actually passing each other route but I cannot ping
to the other side of IPV6 network. Actually RipNG use multicast address to
establish adjencie with their neighbor.
I just wnt to know why this happen, why have to map link-local address
Thanks all
Regards
Mark Stephanus Chandra
IT Consultant
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:17 ART