Virtualbox guests unable to ping(ICMP) web addresses on NAT.

mzs47

Member

Reaction score: 1
Messages: 52

I have two VM guests on a FreeBSD 11.2 host running emulators/virtualbox-ose, one is Debian 9 and another FreeBSD 12. Both VMs have two interfaces one NAT, another host only.
Access to internet works(via NAT of Vbox) and I am able to resolve addresses and install packages, however ping to a website/public address fails to get a reply(pong) on either of them via this NAT network. These guests get a pong on host only network.

I am sharing shell snippet from both guests below, I first ping the VM host IP(192.168.56.1) which is connected to the host only adapter and later gnu.org, which gets resolved via NAT and should get a reply, but no pong comes back.

Debian 9 guest:

Code:
ping -c 3 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
64 bytes from 192.168.56.1: icmp_seq=1 ttl=64 time=0.311 ms
64 bytes from 192.168.56.1: icmp_seq=2 ttl=64 time=0.464 ms
64 bytes from 192.168.56.1: icmp_seq=3 ttl=64 time=0.849 ms

--- 192.168.56.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2032ms
rtt min/avg/max/mdev = 0.311/0.541/0.849/0.227 ms

debian:~$ ping -c 3 gnu.org
PING gnu.org (208.118.235.148) 56(84) bytes of data.

--- gnu.org ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2041ms
FreeBSD 12 guest:


Code:
ping -c 3 192.168.56.1
PING 192.168.56.1 (192.168.56.1): 56 data bytes
64 bytes from 192.168.56.1: icmp_seq=0 ttl=64 time=0.373 ms
64 bytes from 192.168.56.1: icmp_seq=1 ttl=64 time=0.658 ms
64 bytes from 192.168.56.1: icmp_seq=2 ttl=64 time=1.569 ms

--- 192.168.56.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.373/0.867/1.569/0.510 ms


fbsd0:~ % ping -c 3 gnu.org
PING gnu.org (208.118.235.148): 56 data bytes

--- gnu.org ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
 

johnblue

Well-Known Member

Reaction score: 38
Messages: 304

There could be other factors in play but what does the v12 guest think it default route is?

netstat -r
 
Top