在Windows中为套接字使用特定的网络接口

FYI还有另一个问题perform connect() on specific network adapter沿着同一行…

根据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.

所以要回答你的问题(正确的，这个时候)在Windows XP和Windows Server 2003的IP4不，但对于IP6是的。对于Windows Vista和Windows 2008是(某些情况除外)。

也从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
07003

“How to connect a port to a specified
Networkcard?” at
07004.
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
07005

“Strange bind behavior on multihomed
system” at
07006

希望有帮助！