It does make sense though. Say one megabits interface with 20 VLANs. In that
scenario, every VLAN, usually has own link-local address. It is more practical
than "multiple interfaces with same link-local address."
I found this on Juniper router and now assume it is Juniper specific
implementatio
And unless you are on only certain particular devices (e.g. L3 switches)
then the end device won't necessarily have any relevant clue what VLAN it's
on.
I have never seen/heard of an RFC for it either and would certainly wonder
"WHY?". :)
Scott
-Original Message-
From: [EMAIL PROTECTED
Never mind
it is the VLAN number. But which RFC define this?
Thanks all
Dave
- Original Message
From: snort bsd <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; juniper-nsp
Sent: Monday, 28 January, 2008 3:05:59 PM
Subject: IPv6 questions
Hi All:
With link-local IPv6 address, the conver
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 t
4 matches
Mail list logo
