Comment 4 for bug 1825598

Hi,

Upon further investigation. I have come to the conclusion that my host
OS 19.04 network card

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.2.11  netmask 255.255.255.0  broadcast 192.168.2.255
         inet6 fe80::97c7:f9c8:79ec:15d6  prefixlen 64  scopeid 0x20<link>
         ether 50:46:5d:aa:2f:a8  txqueuelen 1000  (Ethernet)
         RX packets 310173  bytes 266065656 (266.0 MB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 254883  bytes 39103611 (39.1 MB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Wont allow bridge mode to Virtualbox on enp2s0.

running iproute on my host os shows weirdness:

steve@Desktop-pc:~$ ip route
default via 192.168.2.1 dev enp2s0 proto dhcp metric 100
169.254.0.0/16 dev enp2s0 scope link metric 1000
192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.11
metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown

Whereas on my working machine ip route shows:

steve@Stevuntutop:~$ ip route
default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.14
metric 600

On Stevuntotop I have a vm set in bridged mode to the adapter that my
host uses. The vm can ping my gateway, thus get the internet.

On my desktop i have a carbon copy of my virtual server on a fresh
install of virtualbox in bridged mode to the nic that my desktop is
using. The vm can ping my other vm but not my gateway. Perhaps my
routing table is in the wrong order. Hence its a bug with network
manager in 19.04.

-Steve

Guess this is a bug that has nothing to do with what i originally thought.

On 2019-04-20 2:56 a.m., Paul White wrote:
> ** Package changed: ubuntu => virtualbox (Ubuntu)
>