The host is a netbook connected by wireless. Setting the guest to NAT largely worked, except that some specific web pages will not load. The sites generally are fine, it's specific to certain locations within them. Maybe it's some sort of problem because the LAN itself is within another NAT? Anyway, that problem doesn't occur if I go to Bridged Adapter but
The "Bridged Adapter" setup only works if "Cable connected" is checked. Otherwise DHCP doesn't do its tricks, whether invoked by dhclient or by
Code: Select all
auto eth1
iface eth1 inet dhcp
What I haven't found documented is what that "Cable connected" checkbox is actually changing - what's the back-end behavior it switches? In my instance it needs to be checked in order for DHCP to work, and for the guest to connect in bridged mode, even though it's a wireless connection (no cable). On the other hand, the adapter being used is "Atheros AR2427 Wireless Network Adapter," so this is a checkbox that can be applied or not when VB knows the connection is wireless.
What is it supposed to do? If I'm using it wrong - as the best way I've found to get things to work - is there a right way I haven't found yet?