From: Roland Bless <roland.bless@kit.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bismark-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ipv6 fe80:: addresses, vlans and bridges... borked?
Date: Mon, 09 May 2011 16:49:03 +0200 [thread overview]
Message-ID: <4DC7FEDF.3030005@kit.edu> (raw)
In-Reply-To: <BANLkTi=ta8EsXSgTnRmES-soB-iOwFF5Ow@mail.gmail.com>
Hi Dave,
On 09.05.2011 05:26, Dave Taht wrote:
> I am modestly stumped as to how to solve this properly. I think it's
> been causing problems with ipv6 for a long time, but I could be wrong.
>
> see http://www.bufferbloat.net/issues/126
>
> Basically although the underlying interfaces do have unique mac
> addresses (for some reason the underlying eth0 interface is sharing a
> mac address with the wlan0 interface??),
> the bridged to a vlan fe80:: addresses are all the same. This strikes me
> as a problem.
It seems that in these cases the ether/link address is also the same,
therefore the interfaces configure all the same link-local address.
Link local addresses are only unique with respect to their link,
i.e., usually you have to specify the interface in addition to the
fe80::/64 destination address, e.g., ping6 fe80::c63d:c7ff:fe8b:6e1a%vlan1
> Is there a standard for renaming fe80:: addresses to represent they are
> interfacing with different vlans?
Maybe that's the wrong question. What is the problem you are trying to
solve? Maybe link local addresses are not the right tool...
Regards,
Roland
next prev parent reply other threads:[~2011-05-09 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 3:26 Dave Taht
2011-05-09 8:14 ` Fred Baker
2011-05-09 14:59 ` Dave Taht
2011-05-09 15:57 ` Fred Baker
2011-05-09 16:14 ` Dave Taht
2011-05-09 16:44 ` Fred Baker
2011-05-09 18:56 ` Dave Taht
2011-05-09 14:49 ` Roland Bless [this message]
2011-05-10 14:30 ` Jeremy Visser
2011-05-11 3:32 ` Dave Taht
2011-05-11 4:40 ` Roland Bless
2011-05-11 13:46 ` Dave Taht
2011-05-11 16:37 ` Rick Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC7FEDF.3030005@kit.edu \
--to=roland.bless@kit.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox