[137271] in North American Network Operators' Group
Re: 10GBASE-T Switches
daemon@ATHENA.MIT.EDU (Karl Auer)
Thu Feb 10 14:55:12 2011
From: Karl Auer <kauer@biplane.com.au>
To: nanog@nanog.org
In-Reply-To: <20110210193343.GA16971@srv03.cluenet.de>
Date: Fri, 11 Feb 2011 06:52:07 +1100
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--=-+KVQ3BDxVT58NTb4xcBS
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Thu, 2011-02-10 at 20:33 +0100, Daniel Roesen wrote:
> Be aware, that IGMP snooping breaks some(!) IPv6 multicast (e.g.
> DHCPv6). Affects whole EX-series and current plan is to fix it sometime
> end of year (Q4 release). If you use IPv4 multicast and need IGMP
> snooping to prevent flooding and plan to use e.g. stateful DHCPv6, that
> might be a showstopper for now and the VLANs where IGMP snooping is
> enabled.
Not disagreeing, I've never met this device, just curious about the
problem and wondering if it is a generic class of problem.
Is this device supposed to be IPv6-capable? If so, IGMP snooping and MLD
snooping should be able to coexist, I'd have thought. In fact, it will
be a major blow for the future of dual-stacking if they can't.
So is the problem of which you speak just a bug, or is it an artifact of
the switch not being IPv6 capable and so limiting broadcasts at the
ethernet level to IGMP-discovered listeners only, ignoring IPv6
multicast listeners? Or something :-)
Also. why does it only affect DHCPv6? Or was that just an example of a
service that would be affected by the problem?
Regards, K.
--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au) +61-2-64957160 (h)
http://www.biplane.com.au/kauer/ +61-428-957160 (mob)
GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156
--=-+KVQ3BDxVT58NTb4xcBS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEABECAAYFAk1UQeAACgkQMAcU7Vc29ocrxwCgn9uvA25cdrc+RWp7fECmv/E+
9t4AniqK3ZKZXfI+PToNl1x2M1I+G3Fu
=aY7l
-----END PGP SIGNATURE-----
--=-+KVQ3BDxVT58NTb4xcBS--
