Re: Linux Guest - Win 10 Host - Bridged Network No...

mmartin0926 · ‎06-29-2018

Hello All,

I have a Linux VM that was created using the VMware Converter from P2V. The linux guest boots up just fine, and everything seems to be working except for Bridged networking. Even though I have bridged networking selected, it still appeared to be using the NAT setting anyway, given the IP Address the VM currently has.

I had noticed that there were no vmnet# adapters showing in the Win10 host. So I uninstalled VMware Player 14.1.1, then I downloaded the newest Player version 14.1.2 from vmware.com. After the install I am seeing 2 "new" network adapters in the Windows host. However, it still appears to have the same result.

I have Bridged Networking and Replicate Physical Network State enabled for the VM but the Virtual Machine is getting an IP Address from VMnet8, shown in the outputs below:

*I tried it without Replicate Physical network state as well, with same result...

Linux Guest shows:

# ifconfig -a
eth0      Link encap:Ethernet HWaddr 00:0C:29:XX:XX:XX
         inet addr:192.168.122.128 Bcast:192.168.122.255 Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe2b:945/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1058 errors:0 dropped:0 overruns:0 frame:0
          TX packets:932 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:102194 (99.7 Kb) TX bytes:91653 (89.5 Kb)
          Interrupt:18 Base address:0x2000
lo        Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1272 (1.2 Kb) TX bytes:1272 (1.2 Kb)

Windows 10 Host shows:

Ethernet adapter VMware Network Adapter VMnet1:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-XX-XX-XX
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c45b:6183:a1a3:d2c6%54(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.130.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, June 29, 2018 5:45:36 PM
   Lease Expires . . . . . . . . . . : Friday, June 29, 2018 6:30:36 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.130.254
   DHCPv6 IAID . . . . . . . . . . . : 905990230
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-CA-90-87-54-E1-AD-4C-97-1E
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . : 00-50-56-XX-XX-XX
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3153:4901:e4a8:4df5%56(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.122.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, June 29, 2018 5:45:39 PM
   Lease Expires . . . . . . . . . . : Friday, June 29, 2018 6:30:39 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.122.254
   DHCPv6 IAID . . . . . . . . . . . : 939544662
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-CA-90-87-54-E1-AD-4C-97-1E
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   Primary WINS Server . . . . . . . : 192.168.122.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Any ideas what could be happening here?

From the Linux guest, if I telnet to one of our switches, and then check who is connected to the switch via telnet, I can see the IP Address of my Win 10 host. So it appears to be using NAT, whether or not I've selected NAT or Bridged.

Thanks in Advance,

Matt

mmartin0926 · ‎07-06-2018

UPDATE: Still was unable to get this working normally. However, found a workaround that I hope someone can tell me why this is working but the "normal" way of bridged isn't working.

I had to download the vmnetcfg.exe file from online as it appears VMWare Workstation Player 14 no longer comes with this file.

Opened the Virtual Network Editor and tried the common fix online of specifically setting bridged (*VMnet0) to a specific NIC, i.e. whichever was currently in use... However, this still did not work and the Guest was still getting the IP Address in the NAT range. So after manually trying each of my NICs with NO luck I tried the following:

- Opened Virtual Network Editor and selected VMnet8, which is the NIC that NAT uses.

- Edited VMnet8 and changed it from "NAT (share host's IP address with VMs" to "Bridged (connect VMs directly to the external network)"

- Then, in the dropdown box to select which NIC to use, I did not have the automatic option. So I set this to my Ethernet adapter.

Now, bridged is working in the VM. But, I don't currently have an option to select my Wireless NIC. The only options its giving me in the dropdown box is Ethernet. So this workaround will only work with a wired connection.

Given the workaround, does anybody know why it would work setting VMnet8 as bridged. But, it's not working when I use VMnet0 as the bridged connection??

Thanks in Advance,

Matt

All

Linux Guest - Win 10 Host - Bridged Network Not Working