Re: Incorrect source IP address on IGMP membership report

2017-12-09 Thread Andrew Lunn
> Hmm, RFC3376 says: > > 4.2.13. IP Source Addresses for Reports > >An IGMP report is sent with a valid IP source address for the >destination subnet. The 0.0.0.0 source address may be used by a >system that has not yet acquired an IP address. Note that the >0.0.0.0 source addre

Re: Incorrect source IP address on IGMP membership report

2017-12-09 Thread Kevin Cernekee
On Sat, Dec 9, 2017 at 8:01 AM, Andrew Lunn wrote: > The choice of IP address for IGMP in Linux is 'interesting'. Try with > multiple IP addresses on the interfaces, addresses with different > scopes, etc. I've seen it reply to the querier using an address from > a different subnet to the incomi

Re: Incorrect source IP address on IGMP membership report

2017-12-09 Thread Andrew Lunn
On Fri, Dec 08, 2017 at 09:25:58PM -0800, Kevin Cernekee wrote: > Closing a multicast socket after the final IPv4 address is deleted > from an interface will generate a membership report that uses the > source IP from a different interface. The following test script, run > from an isolated netns,

Incorrect source IP address on IGMP membership report

2017-12-08 Thread Kevin Cernekee
Closing a multicast socket after the final IPv4 address is deleted from an interface will generate a membership report that uses the source IP from a different interface. The following test script, run from an isolated netns, reproduces the issue: #!/bin/bash ip link add dummy0 type dumm