On Saturday 07 January 2006 23:10, you wrote:
> > Then does this mean that there is no way to ensure that a particular
> > socket can only receive multicast packets which arrived on a specific
> > interface?
> Try SO_BINDTODEVICE.
Ok, thanks!
Bye,
Jori
-
To unsubscribe from this list: send the lin
From: Jori Liesenborgs <[EMAIL PROTECTED]>
Date: Sat, 7 Jan 2006 23:04:06 +0100
> Then does this mean that there is no way to ensure that a particular socket
> can only receive multicast packets which arrived on a specific interface?
Try SO_BINDTODEVICE.
-
To unsubscribe from this list: send the
On Saturday 07 January 2006 22:04, you wrote:
> A bound socket will only receive packets that match the binding.
> If you want to receive packets sent to a particular multicast address,
> you need to bind to that address.
> Group membership is per-interface, not per-socket. You can
From: David Stevens <[EMAIL PROTECTED]>
Date: Sat, 7 Jan 2006 13:04:51 -0800
> A bound socket will only receive packets that match the
> binding. If you want to receive packets sent to a particular
> multicast address, you need to bind to that address.
That's how I see this as well.
-
T
[EMAIL PROTECTED] wrote on 01/07/2006 08:13:17 AM:
> I've encountered the following problem: when a UDP socket was bound
> to a specific interface and a multicast group was joined, no packets
> sent to that multicast group were delivered to the application. If the
> socket was not bound to a spec
