Bridged networking is not working with 6.0.14

[keenerb]

Debian 9 x86_64 host.

I removed Virtualbox 5.2 installation some time ago to tinker with kvm and libvirt. I have subsequently uninstalled kvm and re-installed Virtualbox 6.0 and I have no functional bridged networking.

New VMs I've installed never receive DHCP responses. If I statically assign an IP address to a client, I can ping the server IP address but nothing else on the network.

Any idea what might be going on here? NAT works fine. I'm bridging to physical (non-wireless) connections, neither of the three NICs I have are functional as bridged devices.

The only entries in my vbox.log that seem to reference any NIC configuration or setup are:

00:00:00.363910 E1000#1: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled GC=enabled
00:00:00.364029 IntNet#0: szNetwork={HostInterfaceNetworking-enp1s0f0} enmTrunkType=3 szTrunk={enp1s0f0} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:00.364675 E1000#2: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled GC=enabled
00:00:00.364765 IntNet#1: szNetwork={HostInterfaceNetworking-enp1s0f1} enmTrunkType=3 szTrunk={enp1s0f1} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false

The only error logged is:

ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37

As far as I know there's no host-side setup for bridged networking to work with Virtualbox, is there?

[keenerb]

I have tried other nic types (pcnet II and III) with no change to behaviour.

[socratis]

As far as I know there's no host-side setup for bridged networking to work with Virtualbox, is there?

Of course there is! It's called a Bridged filter kernel module (VBoxNetFlt) and if that's not loaded, then your Bridged-over-anything is not going to work. Here's what going on on my Mint19 host for example:

$ lsmod | grep -i vbox
vboxpci                24576  0
vboxnetadp             28672  0
vboxnetflt             28672  0 <--- This one
vboxdrv               491520  3 vboxpci,vboxnetadp,vboxnetflt

How does your installation logs look like? "/var/log/vbox-setup.log" and "/var/log/vbox-install.log"? Here's what mine look like:

Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.

VirtualBox 6.1.0_BETA2 r134539 installer, built 2019-11-08T15:05:52Z.

Testing system setup...
Installing VirtualBox to /opt/VirtualBox

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
Installation successful

I have tried other nic types (pcnet II and III)

Don't, you're only making things worse.
And Bridged-over-something failing, has nothing to do with what's presented to the guest as a NIC option.

If I statically assign an IP address to a client, I can ping the server IP address but nothing else on the network.

That doesn't sound right. That means that you have a DNS issue with your LAN's router, and/or other networking details. Can you post the output from both Host and Guest of the following command?

• 
  nmcli d show

neither of the three NICs I have are functional as bridged devices.

Does that mean that you have 3 (THREE) NICs on your Host, and none of them can used as a Bridged-over-Ethernet? But they do get an IP themselves?

The only error logged is:

That's a red-herring, you can ignore it.

How about us taking a look at the logs as well? We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[keenerb]

vboxpci                24576  0
vboxnetadp             28672  0
vboxnetflt             28672  1
vboxdrv               479232  4 vboxnetadp,vboxnetflt,vboxpci

I've executed rcvboxdrv setup as well to rebuild the modules.

root@whiptail:/var/log# cat vbox-setup.log
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.

I don't have a vbox-install.log in /var/log

I have no nmcli executable. Looking into what that is and will install it.

The statement regarding PING is correct. My host PC has IP addresses 192.168.1.5, .6, and 1.2.168.1.7 . If I configure a client with ip address, netmask, gateway, and DNS servers appropriate for my network, I can ping all three HOST ip addresses but nothing else on the network. That strikes me as EXCEEDINGLY strange.

I will gather the logs later tonight.

This all worked prior to installing and tinkering with KVM.

[socratis]

Everything looks fine...

I have no nmcli executable. Looking into what that is and will install it.

It's the NextThing™ in showing the info that is needed for a complete network information dump. Much better than 'ifconfig'...

If I configure a client with ip address, netmask, gateway, and DNS servers appropriate for my network

That's what I hope to see from the 'nmcli' info; how "appropriate" your values are.

That strikes me as EXCEEDINGLY strange.

Imagine us that are not in front of your computer!

This all worked prior to installing and tinkering with KVM.

Then maybe KVM isn't completely uninstalled? Maybe there's a filter driver analogous to 'VBoxNetFlt' one?

I will gather the logs later tonight.

They're not crucial, but they would definitely help. Your network configuration in both Host and Guest are more important. The log will just confirm that you're using Bridged-over-???.

[keenerb]

Server nmcli output:

Code: Select all

GENERAL.DEVICE:                         vboxnet0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         0A:00:27:00:00:00
GENERAL.MTU:                            1500
GENERAL.STATE:                          20 (unavailable)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               off

GENERAL.DEVICE:                         enp1s0f0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:36:53:6C
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.5.7/24
IP4.GATEWAY:                            192.168.5.1
IP4.ROUTE[1]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP6.ADDRESS[1]:                         fe80::225:90ff:fe36:536c/64
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         enp1s0f1
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:36:53:6D
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.5.140/24
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         fe80::225:90ff:fe36:536d/64
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --

Guest nmcli output:

Code: Select all

GENERAL.DEVICE:                         enp0s3
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         08:00:27:90:51:5D
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         10.0.2.15/24
IP4.GATEWAY:                            10.0.2.2
IP6.ADDRESS[1]:                         fe80::a00:27ff:fe90:515d/64
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         enp0s8
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         08:00:27:84:72:4A
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.5.8/24
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         fe80::a00:27ff:fe84:724a/64
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         enp0s9
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         08:00:27:4D:5A:46
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         fe80::a00:27ff:fe4d:5a46/64
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --

Code: Select all

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp0s3
allow-hotplug enp0s3
iface enp0s3 inet dhcp

# Bridge network, static IP
auto enp0s8
iface enp0s8 inet static
        address 192.168.5.8/24
        gateway 192.168.5.1

# Bridge network, dhcp
auto enp0s9
allow-hotplug enp0s9
iface enp0s9 inet dhcp

I do have kvm and kvm_intel modules loaded, which is odd. Perhaps that's the problem.

[keenerb]

And server log for VM in question.

For what it's worth, this also affects Windows 10 and Windows Server 2016 guests.

[fth0]

It's the NextThing™ in showing the info that is needed for a complete network information dump. Much better than 'ifconfig'...

Regarding nmcli, I'm not convinced for the following reasons:

1. Although many current linux distributions use the NetworkManager daemon, older setups (or older admins ) sometimes go without it and still use the classic network configuration in /etc/network, which AFAIK is mostly ignored by nmcli.

2. While strongSwan (IPsec VPN) provides a partial NetworkManager integration, the latter is way behind the possibilities of the former and its classical configuration in /etc/ipsec.conf. In consequence, IPsec VPN connections are ignored by nmcli.

3. Network admins are slowly switching from using ifconfig and route to the ip command that provides nearly all needed information. I'm still on my way switching ...