VMware Communities
ygilani
Contributor
Contributor
‎03-16-2018 05:40 AM

Unable to Ping VMWare adapter with source as physical adapter

I have VMWare Workstation Pro setup in NAT mode. Under NAT setting 192.168.168.2 is the gateway IP. I see in host OS (WIndows 10) vmnet8 adapter with IP 192.168.168.1.

My physical adapter (Wireless) gets the IP from DHCP router and is currently assigned an IP 192.168.1.38.

From the guest OS (CentOS 7) I can ping 192.168.1.38 and beyond to internet.

From Host OS I can ping 192.168.168.144 (guest OS) however I can not ping from my Wifi Router (192.168.1.1).

If I ping 192.168.168.144 with source as 192.168.1.38 (physical adapter) it times out.

I cannot also ping 192.168.1.2 from guest OS.

I have reset setting in Network editor and changed back to NAT.

Thank you

0 Kudos
6 Replies
pwilk
Hot Shot
Hot Shot
‎03-16-2018 07:23 AM

Have you tried turning firewalls off on both the guest & host?

Cheers, Paul Wilk
0 Kudos
ygilani
Contributor
Contributor
‎03-16-2018 08:57 AM

Hi Paul,

Firewalls are disabled. Bridged mode works fine, but I want to use NAT. From guest, I can reach internet.

0 Kudos
pwilk
Hot Shot
Hot Shot
‎03-16-2018 09:05 AM

What is the device behind 192.168.1.2 address? Could you post a screenshot of your Workstation network configuration (NAT settings etc.)?

What's the host OS? Can you see a virtual switch in its network settings/control panel?

Cheers, Paul Wilk
0 Kudos
ygilani
Contributor
Contributor
‎03-16-2018 09:19 AM

Hi Paul,

Please see below:

pastedImage_1.png

pastedImage_2.png

pastedImage_3.png

pastedImage_4.png

Guest OS

[root@localhost ~]# ifconfig

ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.168.128 netmask 255.255.255.0  broadcast 192.168.168.255

        inet6 fe80::b286:234d:f051:318c  prefixlen 64  scopeid 0x20<link>

        ether 00:0c:29:3a:f9:84  txqueuelen 1000  (Ethernet)

        RX packets 8260  bytes 11983956 (11.4 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 2764  bytes 177117 (172.9 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1  (Local Loopback)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255

        ether 52:54:00:88:70:0a  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@localhost ~]# ip route

default via 192.168.168.2 dev ens33 proto static metric 100

192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

192.168.168.0/24 dev ens33 proto kernel scope link src 192.168.168.128 metric 100

[root@localhost ~]# ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=128 time=49.8 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=128 time=38.3 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=128 time=56.5 ms

[root@localhost ~]# ping 192.168.1.38 <-- Host adapter

PING 192.168.1.38 (192.168.1.38) 56(84) bytes of data.

64 bytes from 192.168.1.38: icmp_seq=1 ttl=128 time=0.570 ms

64 bytes from 192.168.1.38: icmp_seq=2 ttl=128 time=0.591 ms

64 bytes from 192.168.1.38: icmp_seq=3 ttl=128 time=0.945 ms

[root@localhost ~]# ping 192.168.1.1  <---- router

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=128 time=10.2 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=128 time=10.2 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=128 time=10.6 ms

Host:

pastedImage_12.png

PS C:\WINDOWS\system32> route print

===========================================================================

Interface List

  7...a4 4c c8 eb f2 2f ......Realtek USB GbE Family Controller

17...d6 6a 6a 8f d1 cf ......Microsoft Wi-Fi Direct Virtual Adapter #3

16...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8

  3...d4 6a 6a 8f d1 cf ......Qualcomm QCA61x4A 802.11ac Wireless Adapter

11...d4 6a 6a 8f d1 d0 ......Bluetooth Device (Personal Area Network) #2

  1...........................Software Loopback Interface 1

12...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter

===========================================================================

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination        Netmask          Gateway       Interface  Metric

          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.38     35

        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331

        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331

  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331

      192.168.1.0    255.255.255.0         On-link      192.168.1.38    291

     192.168.1.38  255.255.255.255         On-link      192.168.1.38    291

    192.168.1.255  255.255.255.255         On-link      192.168.1.38    291

    192.168.168.0    255.255.255.0         On-link     192.168.168.1    291

    192.168.168.1  255.255.255.255         On-link     192.168.168.1    291

  192.168.168.255  255.255.255.255         On-link     192.168.168.1    291

        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331

        224.0.0.0        240.0.0.0         On-link      192.168.1.38    291

        224.0.0.0        240.0.0.0         On-link     192.168.168.1    291

  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331

  255.255.255.255  255.255.255.255         On-link      192.168.1.38    291

  255.255.255.255  255.255.255.255         On-link     192.168.168.1    291

===========================================================================

Persistent Routes:

  None

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination      Gateway

12    331 ::/0                     On-link

  1    331 ::1/128                  On-link

12    331 2001::/32                On-link

12    331 2001:0:9d38:6abd:2471:1652:d223:f018/128

                                    On-link

  3    291 fe80::/64                On-link

12    331 fe80::/64                On-link

16    291 fe80::/64                On-link

12    331 fe80::2471:1652:d223:f018/128

                                    On-link

  3    291 fe80::548e:1392:6fea:81d6/128

                                    On-link

16    291 fe80::e09a:e9c5:c5a0:2fae/128

                                    On-link

  1    331 ff00::/8                 On-link

12    331 ff00::/8                 On-link

  3    291 ff00::/8                 On-link

16    291 ff00::/8                 On-link

===========================================================================

Persistent Routes:

  None

PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> ping 192.168.168.128

Pinging 192.168.168.128 with 32 bytes of data:

Reply from 192.168.168.128: bytes=32 time<1ms TTL=64

Reply from 192.168.168.128: bytes=32 time<1ms TTL=64

Reply from 192.168.168.128: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.168.128:

    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32> ping 192.168.168.128 -S 192.168.1.38  <---using source of physical adapter

Pinging 192.168.168.128 from 192.168.1.38 with 32 bytes of data:

Request timed out.

Request timed out.

Ping statistics for 192.168.168.128:

    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),

C:\WINDOWS\system32> tracert -d 192.168.168.2  <--- the trace seems to go out of the wrong interface

Tracing route to 192.168.168.2 over a maximum of 30 hops

  1    38 ms     8 ms     8 ms  192.168.1.1

  2     *

Therefore when pinging from 192.168.1.1 towards 192.168.168.128 (where host PC acts as a router), the ping doesn't work.

0 Kudos
pwilk
Hot Shot
Hot Shot
‎03-16-2018 09:32 AM

Chance the gateway to 192.168.168.1 in NAT settings and it's going to work. Simple as that Smiley Happy

Cheers, Paul Wilk
0 Kudos
ygilani
Contributor
Contributor
‎03-16-2018 09:44 AM

I had tried that , and it didn't work.

[root@localhost ~]# ip route

default via 192.168.168.1 dev ens33 proto static metric 100

192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

192.168.168.0/24 dev ens33 proto kernel scope link src 192.168.168.128 metric 100

C:\WINDOWS\system32> ping 192.168.168.128 -S 192.168.1.38

Pinging 192.168.168.128 from 192.168.1.38 with 32 bytes of data:

Request timed out.

Request timed out.

Ping statistics for 192.168.168.128:

    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),

C:\WINDOWS\system32> ping 192.168.1.1 -S 192.168.1.38

Pinging 192.168.1.1 from 192.168.1.38 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=8ms TTL=64

Reply from 192.168.1.1: bytes=32 time=15ms TTL=64

Reply from 192.168.1.1: bytes=32 time=8ms TTL=64

Reply from 192.168.1.1: bytes=32 time=9ms TTL=64

Ping statistics for 192.168.1.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 8ms, Maximum = 15ms, Average = 10ms

I also lose connectivity from Guest to internet or host if I change the gateway to .1

0 Kudos