From: David Stevens <[EMAIL PROTECTED]>
Date: Thu, 25 Oct 2007 14:58:29 -0700
> I don't see any problem with this. If you're using IP_MULTICAST_IF with
> a bound socket, it forces you to use that interface, anyway.
>
> I'm not sure multicasting works as expected in some other cases with
> bound s
From: David Stevens <[EMAIL PROTECTED]>
Date: Thu, 25 Oct 2007 14:58:29 -0700
> I don't see any problem with this. If you're using IP_MULTICAST_IF with
> a bound socket, it forces you to use that interface, anyway.
>
> I'm not sure multicasting works as expected in some other cases with
> bound s
I don't see any problem with this. If you're using IP_MULTICAST_IF with
a bound socket, it forces you to use that interface, anyway.
I'm not sure multicasting works as expected in some other cases with
bound sockets (looks like there may be some holes to evade the
binding), but that's in old code.
From: Vlad Yasevich <[EMAIL PROTECTED]>
Date: Tue, 23 Oct 2007 14:40:58 -0400
> UDP currently uses skb->dev->ifindex which may provide the wrong
> information when the socket bound to a specific interface.
> This patch makes inet_iif() accessible to UDP and makes UDP use it.
>
> The scenario we a
UDP currently uses skb->dev->ifindex which may provide the wrong
information when the socket bound to a specific interface.
This patch makes inet_iif() accessible to UDP and makes UDP use it.
The scenario we are trying to fix is when a client is running on
the same system and the server and both c
