[160649] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Multicast Ethernet frames not bridging between wired and wireless,

daemon@ATHENA.MIT.EDU (Jared Mauch)
Sun Feb 10 20:26:12 2013

In-Reply-To: <CAOMUSPYof5aLQm=EpLJh0G8uHfDBYDFw0+3nPq2htPTx79qiDQ@mail.gmail.com>
From: Jared Mauch <jared@puck.nether.net>
Date: Sun, 10 Feb 2013 20:25:54 -0500
To: "Christopher J. Pilkington" <cjp@0x1.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

I've seen some Linux boxes in bridge mode do strange things with wireless an=
d ipv6. Using wds mode resolved it. Is the wireless in wds mode?

On Feb 9, 2013, at 2:31 PM, "Christopher J. Pilkington" <cjp@0x1.net> wrote:=


> I've a Netgear 7550 B90 provided by Frontier. (Yes, it's my only choice
> other than VSAT. Rural US. Yes, I am already looking into getting my own
> CPE, but humor me.)
>=20
> Since Frontier doesn't support IPv6, I've linux box on the LAN building an=

> AYIYA tunnel, and doing the usual router thing on the wired Ethernet.
> Everything on the wired side works splendid.
>=20
> Wireless clients didn't seem to want to play. Further digging indicates
> that RA and NS don't cross the bridge from wired to wireless. Manually
> assigning IPv6 address and nailing NDP entries allows ICMPv6 echo request
> to work.
>=20
> Has anyone seen this class of device drop multicast between the wireless
> radio and the wired ethernet switch?
>=20
> Or am I brain dead this morning and missing something obvious?  Heck, I
> even tried disabling WPA2 thinking it was some wonky encryption thing.
>=20
> Thanks,
> -cjp


home help back first fref pref prev next nref lref last post