From: Andrew Lunn <and...@lunn.ch> Date: Tue, 18 Aug 2015 15:36:41 +0200
> We currently take the first address from the interface which is scope > link or higher. > > Historically, the global scope address would of been used, but my > previous fix, which stopped it taking a global scope address from a > different interface altogether under some conditions, changed this > behaviour. > > The first address from the interface, then broke one of my use > case. The querier is only in one of the subnets on this interface, and > using an address from the global scope address range. It then drops > the membership reports when they are sent from the first address on > the interface. This is why i want to restore the previous behaviour, > take the global scope address from this interface. > > The patch works for me and is restoring previous behaviour, but is > that sufficient to make it correct? Preferring link-scope addresses make so much more sense for me. The querier is on the local network, and he can do things like the validity check on the subnet of the source address to try and avoid forged IGMP responses. So if anything I'd be advising you to change the code to prefer link local addresses on the interface and keep avoiding global addresses, as it is the only correct source address selection scheme I can think of for IGMPs. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
