17.10 budgie,mate,lubuntu
Removed NetworkManager -- requirement.
**VBox network
-adapter1 host-only
-adapter2 bridged
/etc/network/interfaces
I have a few VMs, a mix of 17.04 and 17.10. The 17.04s work with this config but the 17.10s do not.
The 17.10s can commuicate with the 192.168* subnets as expected but can't get outside the LAN by either hostname or IP address.
Route from working 17.04 host;
And now from failing host
ip route
Ok so let's get rid of that extra route that the working config doesn't have
Well are the links working at all? Let's check the gateways and the interfaces on the *.123 host.
So what's going on? Where to look next.
I've searched the bug reports for 17.10 and haven't seen anything there so ....
Well I don't know. If anyone sees anything here let me know.
It's obviously not urgent. I'm just tinkering for the sake of exploration but it would be good to see what's failing here.
Thanks
Removed NetworkManager -- requirement.
**VBox network
-adapter1 host-only
-adapter2 bridged
/etc/network/interfaces
Code:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto enp0s8
iface enp0s8 inet static
address 192.168.56.123
auto enp0s3
iface enp0s3 inet static
address 192.168.0.123
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 8.8.8.8 8.8.4.4Code:
cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 127.0.0.53The 17.10s can commuicate with the 192.168* subnets as expected but can't get outside the LAN by either hostname or IP address.
Route from working 17.04 host;
Code:
default via 192.168.0.1 dev enp0s3 onlink
192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.124
192.168.56.0/24 dev enp0s8 proto kernel scope link src 192.168.56.124
test@test:~$ ping -c1 ubuntu.com | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0msAnd now from failing host
Code:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto enp0s8
iface enp0s8 inet static
address 192.168.56.123
auto enp0s3
iface enp0s3 inet static
address 192.168.0.123
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 8.8.8.8 8.8.4.4Code:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53Code:
default via 192.168.0.1 dev enp0s3 onlink
169.254.0.0/16 dev enp0s3 scope link metric 1000
192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.123
192.168.56.0/24 dev enp0s8 proto kernel scope link src 192.168.56.123Code:
ping -c1 ubuntu.com | grep received
ping: ubuntu.com: Temporary failure in name resolutionCode:
# ip route del 169.254.0.0/16
# ip route
default via 192.168.0.1 dev enp0s3 onlink
192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.123
192.168.56.0/24 dev enp0s8 proto kernel scope link src 192.168.56.123
# ping -c1 ubuntu.com | grep received
ping: ubuntu.com: Temporary failure in name resolutionCode:
ping -c1 192.168.1 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
# ping -c1 192.168.123 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
# ping -c1 192.168.56.123 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
# ping -c1 192.168.56.1 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0msSo what's going on? Where to look next.
I've searched the bug reports for 17.10 and haven't seen anything there so ....
Well I don't know. If anyone sees anything here let me know.
It's obviously not urgent. I'm just tinkering for the sake of exploration but it would be good to see what's failing here.
Thanks