Outward ping

[rglegend]

Hi all

I've searched the forum but cannot find a solution to my problem.

My Debian guest OS is running on a Linux host.
It has two network adapters:
1. NAT (ip 10.0.2.15)
2. Host-only (ip 172.16.32.64)

The VM is able to use DNS and TCP but no ICMP
Well, I can ping my host machine, both DHCP servers (10.0.2.2 and 172.16.32.2) but nothing outside my host.
It's able to dig duckduckgo (.) com, but not to ping it.

Can anyone give me a place to continue looking?
I've searched my VM's settings, my host's firewall, VM's firewall, ...
Duckduckgo'd this problem, but nothing came out of it except configuring the machine as it already is...

Thanks in advance!

[rglegend]

VM's ip a:

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:38:85:dc brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global enp0s3
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe38:85dc/64 scope link 
       valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:62:07:8e brd ff:ff:ff:ff:ff:ff
    inet 172.16.32.64/24 brd 172.16.32.255 scope global enp0s8
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe62:78e/64 scope link 
       valid_lft forever preferred_lft forever

[rglegend]

VM's iptables:

Code: Select all

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

[socratis]

2. Host-only (ip 172.16.32.64)

That an interesting, rarely seen choice. Not an issue, but can I ask why?

Try the following "commands" from a Command Prompt on your guest. I've included a sample output, with only the parameters that you should be focusing on:

$ ifconfig
enp0s3    Link encap:Ethernet  HWaddr 08:00:27:40:51:1a  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0

$ route -n
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.2.2        0.0.0.0         UG    100    0        0 enp0s3

or if you prefer "nmcli":

$ nmcli d show
GENERAL.DEVICE:   enp0s3
GENERAL.HWADDR:   08:00:27:40:51:1a   <-- all VirtualBox NICs start with that number
IP4.ADDRESS[1]:   10.0.2.15/24
IP4.GATEWAY:      10.0.2.2
IP4.DNS[1]:       1.1.1.1

Then, once you have the key values, try the following commands:

$ ping <DefaultGateway>             <-- tests your connectivity
$ ping 1.1.1.1                      <-- tests outgoing connectivity
$ ping download.virtualbox.org      <-- tests name resolution

Report any misconfiguration, or any errors from the "ping" commands.

If you can "ping <DefaultGateway>", if you can "ping 1.1.1.1", if you can "ping download.virtualbox.org", VirtualBox is working as it should. You should look elsewhere for your networking connectivity. Look in your host for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc.