Hello!
No, it returns 1 (allow) if there are no filters to explicitly
filter it. I wrote that code. :-)
I see. It did not behave this way old times.
From your mails I understood that current behaviour matches another
implementations (BSD whatever), is it true?
Alexey
-
To unsubscribe
Alexey Kuznetsov [EMAIL PROTECTED] wrote on 09/14/2006 03:30:37 AM:
Hello!
No, it returns 1 (allow) if there are no filters to explicitly
filter it. I wrote that code. :-)
I see. It did not behave this way old times.
From your mails I understood that current behaviour matches
On Thu, 2006-09-14 at 08:39 -0700, David Stevens wrote:
Alexey Kuznetsov [EMAIL PROTECTED] wrote on 09/14/2006 03:30:37 AM:
Hello!
No, it returns 1 (allow) if there are no filters to explicitly
filter it. I wrote that code. :-)
I see. It did not behave this way old
The situation is this:
Two programs have opened IPv4 UDP sockets, set SO_REUSEADDR on them, and
are bound to INADDR_ANY on the same port. One program joins a multicast
group address, the other program joins a different one. When a multicast
packet is sent to this port on one of the group
[EMAIL PROTECTED] wrote on 09/13/2006 07:13:55 AM:
Only
the socket that is bound to the group address to which the packet was
sent should get it.
This is not true on any OS I'm aware of, including the
original sockets multicast implementation on early BSD.
Multicast group
On Wed, 2006-09-13 at 07:32 -0700, David Stevens wrote:
[EMAIL PROTECTED] wrote on 09/13/2006 07:13:55 AM:
This is not true on any OS I'm aware of, including the
original sockets multicast implementation on early BSD.
The current Linux behavior does seem to be consistent with the
Jeff Layton [EMAIL PROTECTED] wrote on 09/13/2006 09:12:23 AM:
Most of the RFC's I've looked at don't seem to have much to say about
how multicasting works at the socket level. Is there an RFC or
specification that spells this out, or is this one of those situations
where things are somewhat
Hello!
IPv6 behaves the same way.
Actually, Linux IPv6 filters received multicasts, inet6_mc_check() does
this.
IPv4 does not. I remember that attempts to do this were made in the past
and failed, because some applications, related to multicast routing,
did expect to receive all the multicasts
Alexey Kuznetsov [EMAIL PROTECTED] wrote on 09/13/2006 01:20:29 PM:
Hello!
IPv6 behaves the same way.
Actually, Linux IPv6 filters received multicasts, inet6_mc_check() does
this.
No, it returns 1 (allow) if there are no filters to explicitly
filter it. I wrote that code. :-)
From: Jeff Layton [EMAIL PROTECTED]
Date: Wed, 13 Sep 2006 12:12:23 -0400
Most of the RFC's I've looked at don't seem to have much to say about
how multicasting works at the socket level. Is there an RFC or
specification that spells this out, or is this one of those situations
where things
10 matches
Mail list logo
