Windows 2012R2 VB Host 20.04.x Ubuntu Guests cant ping past gateway

Discussions about using Linux guests in VirtualBox.
Post Reply
gkasica
Posts: 7
Joined: 19. May 2018, 09:00
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Ubuntu, Debian, Microsoft
Location: Jackson, WI

Windows 2012R2 VB Host 20.04.x Ubuntu Guests cant ping past gateway

Post by gkasica »

I've had Virtual box running here for years on Windows 2012R2 with a couple of Ubunto Guests. I just made 2 new 20.4.x guests in preparation to upgrade mail servers. Neither system can ping past the gateway and obviously, I can't connect to the repositories to update or install anything. I'm using Bridged and see the gateway and ping it but nothing past it. The ISP is Spectrum and I have a block of 29 usable addresses. Other things like me AppleTV have no issues. I'm stumped here is this an Ubuntu VM setup issue(version 20.04.x}, Windows 2012R2 or VB issue (version 6.1.16). This configuration was flawless on 18.04 and once we put in Spectrum Internet it all went south. I can ping the spectrum gateway from Host and Guests but can't connect or ping past it from the VB Guests. The host has no issues. All the other physical devices can connect and ping normally including the VirtualBox Host on Server 2012R2.

What information do you need to see here to assist? I don't have access to things like route or ifconfig as they are in the net-tools package and I can't get to the outside world to load anything.

Attaching hosts file, route, and netplan network setup, etc below as text

Code: Select all

root@eagle:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 eagle

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
root@eagle:~#
root@eagle:~# cat /etc/netplan/00-installer-config.yaml
# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s17:
      addresses:
      - 24.196.87.82/27
      gateway4: 27.196.87.65
      nameservers:
        addresses:
        - 24.196.87.67
        - 24.196.87.68
        - 27.196.87.77
        - 8.8.8.8
        search:
        - netwrx1.com
  version: 2

root@eagle:~# netplan --debug apply
** (generate:2570): DEBUG: 22:17:23.421: Processing input file /etc/netplan/00-installer-config.yaml..
** (generate:2570): DEBUG: 22:17:23.422: starting new processing pass
** (generate:2570): DEBUG: 22:17:23.422: We have some netdefs, pass them through a final round of validation
** (generate:2570): DEBUG: 22:17:23.422: enp0s17: setting default backend to 1
** (generate:2570): DEBUG: 22:17:23.422: Configuration is valid
** (generate:2570): DEBUG: 22:17:23.422: Generating output files..
** (generate:2570): DEBUG: 22:17:23.422: NetworkManager: definition enp0s17 is not for us (backend 1)
(generate:2570): GLib-DEBUG: 22:17:23.422: posix_spawn avoided (fd close requested)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s17 not found in {}
DEBUG:Merged config:
network:
  bonds: {}
  bridges: {}
  ethernets:
    enp0s17:
      addresses:
      - 24.196.87.82/27
      gateway4: 27.196.87.65
      nameservers:
        addresses:
        - 24.196.87.67
        - 24.196.87.68
        - 27.196.87.77
        - 8.8.8.8
        search:
        - netwrx1.com
  vlans: {}
  wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:device enp0s17 operstate is up, not changing
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s17

root@eagle:~# more /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0
search netwrx1.com
root@eagle:~# ifconfig -a

Command 'ifconfig' not found, but can be installed with:

apt install net-tools

root@eagle:~# ping 24.196.87.68
PING 24.196.87.68 (24.196.87.68) 56(84) bytes of data.
64 bytes from 24.196.87.68: icmp_seq=1 ttl=64 time=0.849 ms
64 bytes from 24.196.87.68: icmp_seq=2 ttl=64 time=0.731 ms
64 bytes from 24.196.87.68: icmp_seq=3 ttl=64 time=0.777 ms
64 bytes from 24.196.87.68: icmp_seq=4 ttl=64 time=0.794 ms
64 bytes from 24.196.87.68: icmp_seq=5 ttl=64 time=0.729 ms
^C
--- 24.196.87.68 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4133ms
rtt min/avg/max/mdev = 0.729/0.776/0.849/0.044 ms

root@eagle:~# ping 24.196.87.65
PING 24.196.87.65 (24.196.87.65) 56(84) bytes of data.
64 bytes from 24.196.87.65: icmp_seq=1 ttl=64 time=0.546 ms
64 bytes from 24.196.87.65: icmp_seq=2 ttl=64 time=0.423 ms
64 bytes from 24.196.87.65: icmp_seq=3 ttl=64 time=0.504 ms
64 bytes from 24.196.87.65: icmp_seq=4 ttl=64 time=0.440 ms
64 bytes from 24.196.87.65: icmp_seq=5 ttl=64 time=0.541 ms
64 bytes from 24.196.87.65: icmp_seq=6 ttl=64 time=0.437 ms

--- 24.196.87.65 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5140ms
rtt min/avg/max/mdev = 0.423/0.481/0.546/0.050 ms

root@eagle:~# ping 8.8.8.8
ping: connect: Network is unreachable

Router routing table
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         71.82.126.129   0.0.0.0         UG    0      0        0 eth0
24.196.87.64    0.0.0.0         255.255.255.224 U     0      0        0 br-lan
71.82.126.128   0.0.0.0         255.255.255.128 U     0      0        0 eth0
71.82.126.129   0.0.0.0         255.255.255.255 UH    0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-lan


Kernel IPv6 routing table
Destination                                 Next Hop                                Flags Metric Ref    Use Iface
::/0                                        ::                                      !n    -1     1   348852 lo      
fe80::8d5:2e0f:4ae2:e56f/128                ::                                      UC    0      0     9910 br-lan  
fe80::/64                                   ::                                      U     256    1        0 br-lan  
fe80::/64                                   ::                                      U     256    0        0 eth0    
fe80::/64                                   ::                                      U     256    0        0 eth1    
fe80::/64                                   ::                                      U     256    0        0 ath0    
fe80::/64                                   ::                                      U     256    0        0 ath1    
::/0                                        fe80::201:5cff:fe95:9846                UGDA  1024   0        0 eth0    
::/0                                        ::                                      !n    -1     1   348852 lo      
::1/128                                     ::                                      Un    0      1        0 lo      
fe80::/128                                  ::                                      Un    0      1        0 lo      
fe80::/128                                  ::                                      Un    0      1        0 lo      
fe80::/128                                  ::                                      Un    0      1        0 lo      
fe80::/128                                  ::                                      Un    0      1        0 lo      
fe80::/128                                  ::                                      Un    0      1        0 lo      
fe80::cab4:22ff:fefc:83d/128                ::                                      Un    0      1        0 lo      
fe80::cab4:22ff:fefc:83e/128                ::                                      Un    0      1        0 lo      
fe80::cab4:22ff:fefc:83f/128                ::                                      Un    0      1        0 lo      
fe80::cab4:22ff:fefc:840/128                ::                                      Un    0      1      414 lo      
fe80::cab4:22ff:fefc:840/128                ::                                      Un    0      1    32924 lo      
ff02::1/128                                 ::                                      UC    0      0    23579 eth0    
ff02::1/128                                 ::                                      UC    0      0     2410 br-lan  
ff02::fb/128                                ::                                      UC    0      0    64885 br-lan  
ff02::1:ff11:2670/128                       ::                                      UC    0      0        1 eth0    
ff00::/8                                    ::                                      U     256    2        0 br-lan  
ff00::/8                                    ::                                      U     256    2        0 eth0    
ff00::/8                                    ::                                      U     256    0        0 eth1    
ff00::/8                                    ::                                      U     256    0        0 ath0    
ff00::/8                                    ::                                      U     256    0        0 ath1    
::/0                                        ::                                      !n    -1

Ping FROM Router

PING www.google.com (172.217.1.36): 56 data bytes
64 bytes from 172.217.1.36: seq=0 ttl=112 time=56.067 ms
64 bytes from 172.217.1.36: seq=1 ttl=112 time=53.119 ms
64 bytes from 172.217.1.36: seq=2 ttl=112 time=53.406 ms
64 bytes from 172.217.1.36: seq=3 ttl=112 time=51.033 ms
64 bytes from 172.217.1.36: seq=4 ttl=112 time=52.411 ms

--- www.google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 51.033/53.207/56.067 ms

gkasica
Posts: 7
Joined: 19. May 2018, 09:00
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Ubuntu, Debian, Microsoft
Location: Jackson, WI

Re: Windows 2012R2 VB Host 20.04.x Ubuntu Guests cant ping past gateway

Post by gkasica »

reinstalled both VMs from scratch.
Both appear to be working. No clue what was wrong. I've done the reinstall probably a dozen times each and couldn't ping past the gateway.
Case closed
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 2012R2 VB Host 20.04.x Ubuntu Guests cant ping past gateway

Post by scottgus1 »

Keep good backups of those VMs! :D

Glad you're up and running.
Post Reply