Hi David, all

I went  as far as to see that different Kernel code is responsible for IPv4 and IPv6 implementation.
We closed the issue in current version as a limitation, but of course we would be happy to get rid of that.
Probably it would be a bit easier to get support in  the next version, since we are going to base on another Linux flavor, which is based on latest Kernel.

Michael

-----Original Message-----
From: David Woodhouse [mailto:dwmw2@infradead.org]
Sent: Saturday, May 28, 2011 2:08 AM
To: netdev@vger.kernel.org
Cc: Yuniverg, Michael; Yedvab, Nadav
Subject: Re: SO_BINDTODEVICE inconsistency between IPv4 and IPv6

On Thu, 2011-03-17 at 10:29 +0000, David Woodhouse wrote:

quoted

We've discovered strange behaviour when we listen on in6addr_any and
use SO_BINDTODEVICE to bind to the lo device.

We can connect to any IPv4 address that is local to the machine, on
any interface. (This is true whether we listen on AF_INET6/in6addr_any
and accept IPv4 connections on the IPv6 socket, or whether we just
listen on AF_INET/INADDR_ANY).

The IPv6 behaviour is different — the only IPv6 address that we can
connect to is ::1.

Michael, Nadav ― did you ever get any further with this?

--
dwmw2