I use a notebook normally connected via wireless to a home router. But sometimes I use it remotely with a 3G broadband "dial-up" connection. Vbox guests work fine in the home configuration but not when connected on 3G:
In this case I have an Ubuntu 9.10 64 bit host with vbox 3.1.2 r56127 and a Windows XP SP2 guest running as NAT. When dialled into 3G, the host connects fine - ppp0 is the 3G connection:
Code: Select all
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:24:97:58:d3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1960 (1.9 KB) TX bytes:1960 (1.9 KB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:41.26.41.10 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1592 errors:0 dropped:0 overruns:0 frame:0
TX packets:2099 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1214138 (1.2 MB) TX bytes:424759 (424.7 KB)
wlan0 Link encap:Ethernet HWaddr 00:0d:f0:39:54:71
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wmaster0 Link encap:UNSPEC HWaddr 00-0D-F0-39-54-71-00-00-00-00-00-00-00-00-00-00
UP RUNNING MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Code: Select all
$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 196.207.32.83
nameserver 196.207.32.69
Code: Select all
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapte
r
Physical Address. . . . . . . . . : 08-00-27-3B-1D-E9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.2.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.2
DHCP Server . . . . . . . . . . . : 10.0.2.2
DNS Servers . . . . . . . . . . . : 192.168.1.5
Lease Obtained. . . . . . . . . . : 27 January 2010 12:54:07 PM
Lease Expires . . . . . . . . . . : 28 January 2010 12:54:07 PM
Does virtualbox support supplying the correct DNS server names from "dial up" connections to NAT guests? Thanks.
I'm posting this in the general forum as I don't think it's specific to the type of host or guest. I've also seen the same problem with a linux guest running on a windows host, with earlier versions of vbox, but without investigating the details.