Is there a reliable way in Windows, apart from changing the routing table, to force a newly created socket to use a specific network interface? I understand that bind() to the interface's IP address does not guarantee this.
Asked
Active
Viewed 3.1k times
24
1 Answers
20
(Ok second time lucky..)
FYI there's another question here perform connect() on specific network adapter along the same lines...
According to The Cable Guy
Windows XP and Windows Server® 2003 use the weak host model for sends and receives for all IPv4 interfaces and the strong host model for sends and receives for all IPv6 interfaces. You cannot configure this behavior. The Next Generation TCP/IP stack in Windows Vista and Windows Server 2008 supports strong host sends and receives for both IPv4 and IPv6 by default on all interfaces except the Teredo tunneling interface for a Teredo host-specific relay.
So to answer your question (properly, this time) in Windows XP and Windows Server 2003 IP4 no, but for IP6 yes. And for Windows Vista and Windows 2008 yes (except for certain circumstances).
Also from http://www.codeguru.com/forum/showthread.php?t=487139
On Windows, a call to bind() affects card selection only incoming traffic, not outgoing traffic. Thus, on a client running in a multi-homed system (i.e., more than one interface card), it's the network stack that selects the card to use, and it makes its selection based solely on the destination IP, which in turn is based on the routing table. A call to bind() will not affect the choice of the card in any way.
It's got something to do with something called a "Weak End System" ("Weak E/S") model. Vista changed to a strong E/S model, so the issue might not arise under Vista. But all prior versions of Windows used the weak E/S model.
With a weak E/S model, it's the routing table that decides which card is used for outgoing traffic in a multihomed system.
See if these threads offer some insight:
"Local socket binding on multihomed host in Windows XP does not work" at http://www.codeguru.com/forum/showthread.php?t=452337
"How to connect a port to a specified Networkcard?" at http://www.codeguru.com/forum/showthread.php?t=451117. This thread mentions the CreateIpForwardEntry() function, which (I think) can be used to create an entry in the routing table so that all outgoing IP traffic with a specified server is routed via a specified adapter.
"Working with 2 Ethernet cards" at http://www.codeguru.com/forum/showthread.php?t=448863
"Strange bind behavior on multihomed system" at http://www.codeguru.com/forum/showthread.php?t=452368
Hope that helps!
-
Thanks, Unless I am missing something, neither answer is relevant, as SO_BINDTODEVICE is not relevant to windows. I suspect your summary is correct though, even though I do not have the evidence. – Ofir Jan 18 '10 at 11:56
-
Oops right you are! Updated my answer above with better info - sorry! – Ezz Jan 18 '10 at 16:18
-
Note that the weak and strong host models do not affect how traffic sent from a socket is routed. I.e. the strong host model ensures that traffic leaving a network adapter uses that adapter's assigned IP address, but does not affect how the network stack in the host itself selects the outgoing adapter to actually use. This is actually explained in "The Cable Guy" link above, as well as on Wikipedia: https://en.wikipedia.org/wiki/Host_model – Peter Duniho Feb 09 '16 at 08:22
-
In certain protocols, such as with icmpv6 neighbor discovery, it is possible to send packets with the unspecified address (i.e. `::`) as the source. A router solicitation message for instance might have (dst `ff02::2` (link local all routers), and `::` as source). If one opened a raw IPv6 socket on windows and sent such a packet, would it go out on all interfaces? Is the implication in this case that there is no other way to restrict the output interface besides forcing the src to be the interface's link-local IP? – init_js Oct 14 '16 at 16:37
-
1So, 11 years later, the best answer is still "Not possible"? – ancajic Mar 09 '21 at 11:21