My laptop (MacOSX) has a network interface for VPN. I am rarely connected to VPN. However, DevTest seems intent on binding to this network interface instead of my en0. My laptop is a DHCP client, so I can't rely on binding to an IP address; the en0 is most likely to be functioning, but when I'm not connected to a network I would need to force connection elsewhere (lo0 or possibly my vmware DHCP network interface).
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
<snipped IP address information>
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
<various other network interfaces>
gpd0: flags=8862<BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1400
My VPN network interface isn't even UP, and yet DevTest is trying to bind to it! How do I force DevTest components to bind to the IP address that is allocated to a specific network interface?
This is on DevTest 9.5, although I noticed the same behaviour in coordinator and simulator in DevTest 9.1.