Ripping my hair out - Bridged network, no internal comms possible

[Griffin]

Just when I think I have this fixed it stops working again. Cannot communicate at all between host and guest...

Host - WIndows 10 Pro 1709 16299.309
VB - Version 5.2.8 r121009 (Qt5.6.2), 5.2.8 Guest Additions installed
Guest - Linux Ubuntu 17.10

Bridged Network adapter only
Host firewall off for private and domain networks'
Guest has full internet access

Host Config...

Code: Select all

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : AC-22-0B-BF-E6-92
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.150(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 1.1.1.1
                                       8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 0A-00-27-00-00-02
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::7493:6b58:fe32:3e51%2(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.244.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 50987047
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-3A-90-50-AC-22-0B-BF-E6-92
   DNS Servers . . . . . . . . . . . : 8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Guest Network config...

Code: Select all

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.102  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 08:00:27:79:b4:ab  txqueuelen 1000  (Ethernet)
        RX packets 726  bytes 342644 (342.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 752  bytes 177697 (177.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 388  bytes 61034 (61.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 388  bytes 61034 (61.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.71.10.6  netmask 255.255.255.255  destination 10.71.10.5
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 633  bytes 272942 (272.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 648  bytes 105998 (105.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Cannot ping between either host nor guest. Cannot communicate with the deluge web interface on port 8112 on the guest from the host.

I'm at my wits end trying to work out this voodoo.

[socratis]

Guest has full internet access

Then VirtualBox has done its job, it's working as it should. After that, and since you're using Bridged mode (aka the guest is just another computer in your LAN), it's something outside of the scope of VirtualBox.

Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

[Griffin]

Well, it's not firewall as that is disabled, and it's not IPTables...

sudo iptables -L
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
PIA_KILLSWITCH_OUTPUT_RULES all -- anywhere anywhere

Chain PIA_KILLSWITCH_OUTPUT_RULES (1 references)
target prot opt source destination
RETURN all -- anywhere 127.0.0.0/8
RETURN all -- anywhere anywhere
DROP all -- anywhere anywhere

This is a very clean install of Ubuntu so I'm a little stuck on this one. More confusing is that for a while it was working just fine and then just stopped without any configuration changes.

[Griffin]

I think my VPN killswitch is buggy, I 'think' if it gets triggered, even when I reboot the machine or restablish the connection I'm not sure it fully resets. I think that was the problem, I'll just see how it goes as it appears to be working again now.