Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 182126

How to ping a computer inside a subnet setup using vmware's virtual network editor connected via NAT?

$
0
0

Problem: Guests VM have intranet connectivity, but are isolated from the host.

My Computer runs 3 VMs: vmInfra(10.0.99.99), vmPrime(10.0.99.11) and vmDeux(10.0.99.12). The host can't ping any VM and vice versa! Here's the basic structure of my network:

 

NetworkStructure.jpg

The output of pings are:

 

 

# ping 10.0.99.2

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

From 10.0.99.1 icmp_seq=1 Destination Host Unreachable

From 10.0.99.1 icmp_seq=2 Destination Host Unreachable

From 10.0.99.1 icmp_seq=3 Destination Host Unreachable

From 10.0.99.1 icmp_seq=4 Destination Host Unreachable

From 10.0.99.1 icmp_seq=5 Destination Host Unreachable

From 10.0.99.1 icmp_seq=6 Destination Host Unreachable

^C

--- 10.0.99.2 ping statistics ---

7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6158ms

pipe 4

 

I just created a subnet using the VMware Virtual Network Editor, that generated a /etc/vmware/vmnet99/dhcpd/dhcpd.conf file:

 

allow unknown-clients;
default-lease-time 1800; # default is 30 minutes
max-lease-time 7200; # default is 2 hours

subnet 10.0.99.0 netmask 255.255.255.0 {
  range 10.0.99.128 10.0.99.254;
  option broadcast-address 10.0.99.255;
  option domain-name-servers 10.0.99.2;
  option domain-name localdomain;
  default-lease-time 1800; # default is 30 minutes
  max-lease-time 7200; # default is 2 hours
  option netbios-name-servers 10.0.99.2;
  option routers 10.0.99.2;
}
host vmnet99 {
  hardware ethernet 00:50:56:C0:00:63;
  fixed-address 10.0.99.1;
  option domain-name-servers 0.0.0.0;
  option domain-name "";
  option routers 0.0.0.0;
}

 

My NAT Settings look like:

 

NAT Settings.png

 

The output of `ifconfig` on my host is:

 

        # ip route show

        default via 192.168.1.1 dev wlo1 proto static metric 600

        10.0.99.0/24 via 10.0.99.2 dev vmnet99

        172.16.8.0/24 dev vmnet1 proto kernel scope link src 172.16.8.1

        172.16.33.0/24 dev vmnet8 proto kernel scope link src 172.16.33.1

192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.73 metric 600

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000

    link/ether 3c:52:82:b9:05:5f brd ff:ff:ff:ff:ff:ff

3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether 3c:95:09:de:4e:8d brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.73/24 brd 192.168.1.255 scope global dynamic wlo1

       valid_lft 85876sec preferred_lft 85876sec

    inet6 fe80::6528:e383:1754:9aef/64 scope link

       valid_lft forever preferred_lft forever

4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000

    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff

    inet 172.16.8.1/24 brd 172.16.8.255 scope global vmnet1

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fec0:1/64 scope link

       valid_lft forever preferred_lft forever

5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000

    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff

    inet 172.16.33.1/24 brd 172.16.33.255 scope global vmnet8

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fec0:8/64 scope link

       valid_lft forever preferred_lft forever

6: vmnet99: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000

    link/ether 00:50:56:c0:00:63 brd ff:ff:ff:ff:ff:ff

    inet 10.0.99.1/24 brd 10.0.99.255 scope global vmnet99

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fec0:63/64 scope link

       valid_lft forever preferred_lft forever

 

I can't figure out what is wrong with my config that prevents the host from even pinging the Gateway NAT device, let alone the VMs!

 

Message was edited by: Somenath Sinha to update the output of `ip addr show`.


Viewing all articles
Browse latest Browse all 182126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>