netdev - Re: IGMP joins come from the wrong SA/interface

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: <20140119181806.GC16462@order.stressinduktion.org>
Date:	Sun, 19 Jan 2014 19:18:06 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	"Steinar H. Gunderson" <sgunderson@...foot.com>
Cc:	netdev@...r.kernel.org
Subject: Re: IGMP joins come from the wrong SA/interface

On Sat, Jan 18, 2014 at 08:11:07PM +0100, Steinar H. Gunderson wrote:
> It doesn't matter if I drop the “multicast” token from the ip route line.
> Behavior is still exactly the same; it comes out of eth0 instead of eth0.2,
> with the wrong source address.
> 
> This used to work, once upon a time, but I fear it broke during a
> kernel upgrade. It's hard for me to say exactly when; probably
> a few months ago. Any ideas?

I currently only remember one commit 0a7e22609067ff ("ipv4: fix
ineffective source address selection") which did affect multicast source
address selection in recent times.

Maybe try a revert?

Greetings,

  Hannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html