(usagi-users 03627) Re: IPv6 multicast socket specific binding bug

[Stig Venaas <stig.venaas@xxxxxxxxxx>]

David Stevens wrote:
> Hoerdt,
>         You're saying you don't like the way multicast socket semantics
> were defined more than 15 years ago.
>         I think it's an equally valid argument that you shouldn't use 
> INADDR_ANY
> unless you really mean *any* address-- bind to a unicast address, and you 
> won't
> have that "problem."
>         But it doesn't matter -- making Linux incompatible with IPv4 
> sockets and all
> other sockets implementations isn't a good idea.

Yes, I believe this is standard behaviour as well.

I've been wondering how this should behave when using the source
filtering API. I expect that when joining some specific sources on one
socket, you would still get everything on another (if bound to right
port and INADDR_ANY).

Some related questions below.

If you use source filtering API and do include mode with (S,G), then I
assume you would not receive from another source for the same group.
Would/should you still receive multicast for other groups (if say some
other group is joined on another socket and the bind address/port
matches...)?

Would a possible work-around be to use source filtering API and join a
non-existent source to prevent receiving packets on the other socket? :)
I suppose you can't set an include mode source filter with no sources to
 block everything.

Stig

> 
>                                                 +-DLS
> 
>