0 Members and 1 Guest are viewing this topic.
iface eth0 inet dhcp
if you are using the network-manager, then /etc/network/interfaces should contain only the loopback network interface only
which network card was chosen for the guest system in virtualbox settings?
Did the upgrade bring anytging related to systemd and/or networkrelated.
What is your desktop-environment?
why not just use standard NAT in vbox?
balken@siduction:~$ ping google.comping: unknown host google.combalken@siduction:~$ sudo ifup eth0[sudo] password for balken: Internet Systems Consortium DHCP Client 4.3.0Copyright 2004-2014 Internet Systems Consortium.All rights reserved.For info, please visit https://www.isc.org/software/dhcp/Listening on LPF/eth0/08:00:27:38:13:feSending on LPF/eth0/08:00:27:38:13:feSending on Socket/fallbackDHCPREQUEST on eth0 to 255.255.255.255 port 67DHCPACK from 10.126.0.1RTNETLINK answers: File existsbound to 10.126.0.178 -- renewal in 1356 seconds.balken@siduction:~$ ping google.comPING google.com (74.125.135.101) 56(84) bytes of data.64 bytes from ni-in-f101.1e100.net (74.125.135.101): icmp_seq=1 ttl=53 time=24.9 ms64 bytes from ni-in-f101.1e100.net (74.125.135.101): icmp_seq=2 ttl=53 time=24.4 ms^C--- google.com ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 1001msrtt min/avg/max/mdev = 24.438/24.708/24.979/0.312 msbalken@siduction:~$ cat /etc/network/interfaces# This file describes the network interfaces available on your system# and how to activate them. For more information, see interfaces(5).# The loopback network interfaceauto loiface lo inet loopbackiface eth0 inet dhcpbalken@siduction:~$