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  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]
Date:   Tue, 24 Jan 2017 12:41:19 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     linus.luessing@...3.blue
Cc:     netdev@...r.kernel.org, stephen@...workplumber.org, nbd@....name,
        nikolay@...ulusnetworks.com, bridge@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: [PATCH net-next v5] bridge: multicast to unicast

From: Linus Lüssing <linus.luessing@...3.blue>
Date: Sat, 21 Jan 2017 21:01:32 +0100

> From: Felix Fietkau <nbd@....name>
> 
> Implements an optional, per bridge port flag and feature to deliver
> multicast packets to any host on the according port via unicast
> individually. This is done by copying the packet per host and
> changing the multicast destination MAC to a unicast one accordingly.
> 
> multicast-to-unicast works on top of the multicast snooping feature of
> the bridge. Which means unicast copies are only delivered to hosts which
> are interested in it and signalized this via IGMP/MLD reports
> previously.
> 
> This feature is intended for interface types which have a more reliable
> and/or efficient way to deliver unicast packets than broadcast ones
> (e.g. wifi).
> 
> However, it should only be enabled on interfaces where no IGMPv2/MLDv1
> report suppression takes place. This feature is disabled by default.
> 
> The initial patch and idea is from Felix Fietkau.
> 
> Signed-off-by: Felix Fietkau <nbd@....name>
> [linus.luessing@...3.blue: various bug + style fixes, commit message]
> Signed-off-by: Linus Lüssing <linus.luessing@...3.blue>

I'm not completely happy that things have progressed this way, however
I don't have a better solution to suggest.

Powered by blists - more mailing lists