From: Dave Taht <dave.taht@gmail.com>
To: Jeremy Visser <jeremy@visser.name>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ipv6 fe80:: addresses, vlans and bridges... borked?
Date: Tue, 10 May 2011 21:32:55 -0600 [thread overview]
Message-ID: <BANLkTi=KGJ3GGJUQeuPpiJHKMcC5PCnoAA@mail.gmail.com> (raw)
In-Reply-To: <4DC94BF6.5060302@visser.name>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Tue, May 10, 2011 at 8:30 AM, Jeremy Visser <jeremy@visser.name> wrote:
> Dave Taht said:
> > the bridged to a vlan fe80:: addresses are all the same. This strikes me
> > as a problem.
>
> You never reference link-local address by themselves anyway — they are
> always referenced with their scope ID for context. So your addresses are
> unique after all:
>
> fe80::c63d:c7ff:fe8b:6e1a%br-lan
> fe80::c63d:c7ff:fe8b:6e1a%br-guest
> fe80::c63d:c7ff:fe8b:6e1a%br-meshlink1
> fe80::c63d:c7ff:fe8b:6e1a%br-meshlink2
>
1) in a wireshark analysis, the %interface part is lost
2) we have 2^64 possible choices for fe80 addresses. I don't see what having
them all be the same buys me.
3) It worries me in the babel routing protocol
4) My bridges are misbehaving over ipv6 in the general case and I'm willing
to grasp at straws.
> Forgive me if I am stating the obvious or misunderstanding your point.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1876 bytes --]
next prev parent reply other threads:[~2011-05-11 3:25 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
2011-05-10 14:30 ` Jeremy Visser
2011-05-11 3:32 ` Dave Taht [this message]
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='BANLkTi=KGJ3GGJUQeuPpiJHKMcC5PCnoAA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jeremy@visser.name \
/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