The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
It looks like I can do it with a simple bind() command. I never got into the routine of using bind with UDP, I just let the system figure it out. It looks like that I can use bind though to specify the correct IP address to send from.
Not a programmer, but since I pretty much search google for a living, I did a run and got a bunch of forum posts about "specifying the source IP on bind" and this bit from MS on NLA which is at least spells out the old methods to do what you want, even if it doesn't tell you how to implement them.
In the past, developers had to obtain information about a logical network interface, and therefore make decisions about network connectivity, based on a multitude of disparate network information. In those circumstances, developers had to choose the appropriate network interface based on the IP address, the subnet of the interface, the Domain Name System (DNS) name associated with the interface, the MAC address of a NIC, a wireless network name, or other network information.
Posts
- doh! too late!