The topology: Physical router (IP 192.168.1.25/24) connects to Host Machine (IP 192.168.1.1/24) running a VM (IP 192.168.1.2/24).
The issue: Using bridged networking, the VM cannot connect through the host's physical network adapter to the router - all are in the same subnet.
I am using bridged networking to connect a virtual server to a physical network, but I'm confused about what IP addresses to use on the host's physical NIC and the guest's virtual NIC. To my understanding, both the physical host's NIC and the guest OS's virtual NIC need to be on the same subnet. So if I assign 192.168.1.1/24 to the physical NIC on the host machine and 192.168.1.2/24 to the virtual NIC inside my virtual guest OS (using Network properties), the guest OS should be able to communicate with the outside real network. But it can't. However, I have noticed that if I use "Obtain an IP address automatically" for my host NIC, it is assigned an automatic address of 169.254.1.1 (an APIPA address). My virtual network adapter has been assigned an address of 192.168.1.2/24 inside my guest OS. And it can communicate with a router that the host machine is connected to with an interface address of 192.168.1.25/24. That doesn't make any sense.
My understanding is that when using bridged networking, the guest OS has a virtual NIC that connects to a virtual switch (VMnet0). The host OS has a real physical NIC that connects to the virtual switch (VMnet0). Then doesn't it follow that both the host's physical NIC and the guest's virtual NIC need to have IP addresses assigned within the same subnet in order to communicate? However, as stated, with those settings the guest OS cannot communicate thru the host's physical NIC to the outside world. But when I assign the host's physical NIC an automatic address (when ends up being 169.254.1.1 when checked with ipconfig), communication works. Can anyone explain this? Many thanks!