[102141] in North American Network Operators' Group
Re: IPv6 questions
daemon@ATHENA.MIT.EDU (Erik Nordmark)
Tue Jan 29 13:45:23 2008
Date: Tue, 29 Jan 2008 10:43:45 -0800
From: Erik Nordmark <erik.nordmark@sun.com>
To: snort bsd <snortbsd@yahoo.com.au>
CC: nanog@merit.edu, juniper-nsp <juniper-nsp@puck.nether.net>
In-Reply-To: <280345.13157.qm@web38104.mail.mud.yahoo.com>
Errors-To: owner-nanog@merit.edu
snort bsd wrote:
> Never mind
>
> it is the VLAN number. But which RFC define this?
I've never seen an IPv6 RFC specify to put the VLAN number in the
link-local address.
Thus this must be an (odd) choice made by some implementation. Perhaps
the implementation somehow requires that all the link-local addresses
for all its (sub)interfaces be unique, even though the RFCs assume that
the implementation should be able to deal with multiple interfaces with
same same link-local address.
Erik
> Thanks all
>
> Dave
>
> ----- Original Message ----
> From: snort bsd <snortbsd@yahoo.com.au>
> To: nanog@merit.edu; juniper-nsp <juniper-nsp@puck.nether.net>
> Sent: Monday, 28 January, 2008 3:05:59 PM
> Subject: IPv6 questions
>
>
> Hi All:
>
> With link-local IPv6 address, the converting from MAC-48 to EDU-64
> address format (FF FE stuffing). How does the VLAN tags affect the
> conversion?
>
> With the rule of FF FE stuffing, I can see clearly work on the ptp
> interfaces. But on those Ethernet based VLANs, it doesn't seem to follow
> that pattern:
>
> Current address: 00:90:69:4a:b9:5d, Hardware address: 00:90:69:4a:b9:5d
>
> well, i assume the link-local should be fe80::290:69ff:fe4a:b95d/64.
> actually, it shows:
>
> Destination: fe80::/64, Local: fe80::290:6903:94a:b95d
>
> how does the router get this 03 09 instead of ff fe?
>
> Thanks all
>
>
>
>
>
>
>
>
> Make the switch to the world's best email. Get the new Yahoo!7
> Mail now. www.yahoo7.com.au/worldsbestemail
>
>
>
>
>
>
>
> Make the switch to the world's best email. Get the new Yahoo!7 Mail now. www.yahoo7.com.au/worldsbestemail
>
>
