LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   General (https://www.linuxquestions.org/questions/general-10/)
-   -   VMWare's bridging vs Window's bridging - routing is messed up when Windows bridging (https://www.linuxquestions.org/questions/general-10/vmwares-bridging-vs-windows-bridging-routing-is-messed-up-when-windows-bridging-639910/)

brenan99 05-04-2008 10:24 PM

VMWare's bridging vs Window's bridging - routing is messed up when Windows bridging
 
I was wondering what the difference is between windows MAC bridging and VMWare's bridging. My network is somewhat convoluted (well it is to me) so please bear with me as I describe the scenario.

I have a machine with an ethernet connection going to the Internet (we'll call it interface0) and another one going to the local lan (interface1). On the local lan there is a router that also links up to the Internet (I live in a dorm room).

Interface0 is set to get a DHCP address from the ISP, while interface1 has been assigned a static ip address (for the 192.168.0.0 subnet) with no default route set. Thus all traffic not destined for the 192.168.0.0 subnet is routed through interface0.

I have VM-Ware installed on my machine and using its built-in bridging, call that one interface2, I bridged it to interface1. In Vmware, my virtual machine was able to get an address on the 192.168.0.0 subnet via dhcp from the router, and all internet-destined traffic was directed through the router rather than through interface0 (which is what I wanted).

However, lately I needed to change this setup; I took down VMWare's built-in bridging interface (interface2) and created a new non-bridged interface (we'll call this one interface3) (I disabled the NAT and DHCP vmware services of course and changed my vm to use that interface3 instead of interface2).

I then bridged interface1 and interface3 (and then gave the bridged interface the same static ip that interface1 had used) with Window's MAC bridging in an attempt to create the same effect as I had with vmware's built-in bridging using interface2. However, I noticed that although I can get an ip on the vm for the 192.168.0.0 subnet, ping all machines on my local lan and that the default router is correctly set to be the router on the local lan, wireshark captures show that if I try to ping google, no packets are sent by the vm over the local lan.

I was suspicious of where the packets were going so I enabled IP forwarding in windows and noticed that my ping packets from the vm were being directed out interface0 (which of course doesn't work)!

My question is how can i get Window's bridge to have the same behavior as VMware's bridge? Or is this at all possible? What is the difference I'm missing?


All times are GMT -5. The time now is 12:28 PM.