netdev - Re: [PATCH iproute2-next 06/17] bridge: vlan: add global mcast_igmp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87pmtuoulz.fsf@gmail.com>
Date:   Tue, 31 Aug 2021 11:02:00 +0200
From:   Joachim Wiberg <troglobit@...il.com>
To:     Nikolay Aleksandrov <razor@...ckwall.org>, netdev@...r.kernel.org
Cc:     roopa@...dia.com, dsahern@...il.com,
        Nikolay Aleksandrov <nikolay@...dia.com>
Subject: Re: [PATCH iproute2-next 06/17] bridge: vlan: add global mcast_igmp_version option

Hi Nik,

awesome to see this patchset! :-)  I've begun setting things up here
for testing.  Just have a question about this:

On Thu, Aug 26, 2021 at 16:05, Nikolay Aleksandrov <razor@...ckwall.org> wrote:
> Add control and dump support for the global mcast_igmp_version option
> which controls the IGMP version on the vlan (default 2).

Why is the default IGMPv2?  Since we support IGMPv3, surely that should
be the default, with fallback to IGMPv2 when we detect end devices that
don't support v3?

The snooping RFC refers back to the IGMPv3 RFC

  https://datatracker.ietf.org/doc/html/rfc3376#section-7

I noticed the default for MLD is also set to the older version v1, and
I'm guessing there's a reasoning behind both that I haven't yet grasped.

Best regards
 /Joachim