I'm running a virtual machine under Fusion (1.1) in bridged mode on my macbook pro running Leopard. I connect to the internet through my wireless connection. I need to connect to a server via the wired connection. The wired connection is on the 192.168.2.x subnet, and the wireless connection is on the 192.168.1.x subnet.
Here's the question: I have an application that needs to communicate with the server on the 192.168.2.x subnet (at 192.168.2.2, specifically). If I turn off the wireless connection, it works fine. However, when I turn on the wireless connection, it stops working (and when I look at network traces, all the packets start going out on the wireless interface).
I'm confused as to why this is happening as when I run "route get 192.168.2.2", the interface it reports for the route is the wired interface (which is where the packets should be going but aren't). Does Fusion automatically send out VM packets on whatever interface it thinks is connected to the internet? Is there a way to control routing of packets originating from the VM?
Any help is appreciated.
Thanks,
Nick
Here's the question: I have an application that needs to communicate with the server on the 192.168.2.x subnet (at 192.168.2.2, specifically). If I turn off the wireless connection, it works fine. However, when I turn on the wireless connection, it stops working (and when I look at network traces, all the packets start going out on the wireless interface).
I'm confused as to why this is happening as when I run "route get 192.168.2.2", the interface it reports for the route is the wired interface (which is where the packets should be going but aren't). Does Fusion automatically send out VM packets on whatever interface it thinks is connected to the internet? Is there a way to control routing of packets originating from the VM?
Any help is appreciated.
Thanks,
Nick