Ask your questions here.
Fri Sep 26, 2014 4:39 pm
Oops. The VM uses the host's network interface, and since that is already connected, the VM doesn't need the password for the router.
Did this in the live snapshot running in vbox:
It seems like the problem has something to do with NetworkManager and/or resolvconf. If I kill NetworkManager, set up eth0 in etc/network/interfaces, and set the nameserver in etc/resolv.conf (against the advice in the comments in that file), and start the interface with 'ifup eth0', the network connection works correctly.
I tried adding the dns server in the IPv4 tab in the network manager applet (you have to click on the wrench to get there), with and without adding a nameserver to resolv.conf, but that didn't work.
What did work when using only the network manager applet and not editing any files, was to go to the IPv4 tab, select Manual from the drop-down menu, and set up static IP. When I looked in resolv.conf after getting connected, it showed 'nameserver 127.0.1.1' which is the same as when running the installed (in vbox) kubuntu.
I'm considering this thread partially solved. There are a few workarounds, but I haven't actually solved the problem with network manager. This is deja-vu for me, because it was a problem with network manager and resolv.conf that led to my very first post at fdn around six years ago. The solution at that time was to remove network manager, since I was using the interfaces file for a static IP. That's still a possible solution.
So, to the OP and the additional poster with what looks like the same problem, here are some options...
You can set up a static IP address in the network manager applet and get online. You need to know the address of the router you're using to do this. That gets used as the gateway and possibly as the dns server. You probably need to know the IP addresses of any other computers on that local network, so you don't choose one that's in use.
You could just kill NetworkManager and then set up static IP in the interfaces file. Except that I could not do this a second time. When I rebooted the iso and tried to repeat it, nm kept coming back. I don't know what I did the first time to keep nm killed. Too bad - I wanted to test dhcp setup in etc/network/interfaces.
You could remove the network-manager package to set up static IP or dhcp in the interfaces file, or you could replace it with a different network managing program. (maybe wicd, ceni, or others that I can't remember right now.) This should be done in the installed system before you create your snapshot.
Maybe switch to Xubuntu? Debian?
There's probably some other field in the nm-applet that needed to be filled out to get it to work. I didn't try every combination of everything in there. You could experiment with it.