Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #1578

Re: VirtualBox Windows guest loses DHCP and DNS

Show all headers | View raw

In article <slrnk298v4.441.dyrmak@paletuvier.terre>,
dyrmak@orange.fr.invalid (dyrmak) writes:

> En 53 lignes Charlie Gibbs a écrit
> dans news:2620.631T181T7603234@kltpzyxm.invalid
> le mercredi, 01 août 2012 à 22:40:03 :
>
>> Once back from vacation, I fired up my own laptop, which I've set
>> up the same way (except that my host is Mint 12 LXDE), and got
>> the identical failure.  On the other hand, my desktop box, which
>> runs Slackware 13.37 and has a Win2000 guest under VirtualBox,
>> continues to have perfect network communications for both host
>> and guest.  (For what it's worth, it's wired, not wireless.)

Before we begin, another data point: I tried installing VMware
Player on my wife's machine.  It was one of the slickest installs
that I've ever seen - but once the Windows guest machine came up,
it had identical networking problems to the VirtualBox guests.
So whatever the problem is, it's not a bug in VirtualBox - which
comes as a great relief to me, since I now know that my production
VirtualBox guest, which is on a wired network, is in no danger of
spontaneously going down.

> For what it's worth, have you tried a wired connection on the
> ailing laptop ? it is known to this date that bridging a guest
> machine with wireless is not possible.

I had tried plugging a network cable into my laptop, but it made
no difference.  I then realized, however, that I had configured
the guest machine with only a wireless interface (wlan0).  When
I added a second emulated interface, this time to a wired network
(eth0), it came up properly.  In fact, when I reconfigured the
interfaces to use DHCP, they both worked - but only if the Ethernet
cable was plugged in.  As you say, it isn't able to bridge a
wireless interface - although a wired interface, if present,
seems to provide the magic needed by the wireless one.

As an additional experiment, I disabled the wireless interface
in the Actiontec router, dug out my old wireless access point,
and plugged it back into my switch, restoring my original
wireless configuration.  This too failed to work on a bridged
wireless connection.

I've found a number of references on the net to procedures
for getting bridging to work, but they look pretty involved
and I've already spent more time than I can afford on this
so I'll presuade my wife to limp along until another day.

But I'll leave you with the following brain-teaser: why did
wireless bridging work perfectly for several months, both on the
old and the new hardware?  What is the magic that used to be there,
but which can now only be had by plugging in an Ethernet cable?

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

VirtualBox Windows guest loses DHCP and DNS "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2012-08-01 12:40 -0800
  Re: VirtualBox Windows guest loses DHCP and DNS dyrmak <dyrmak@orange.fr.invalid> - 2012-08-10 06:02 +0000
    Re: VirtualBox Windows guest loses DHCP and DNS "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2012-08-10 15:05 -0800
      Re: VirtualBox Windows guest loses DHCP and DNS dyrmak <dyrmak@orange.fr.invalid> - 2012-08-13 06:18 +0000
        Re: VirtualBox Windows guest loses DHCP and DNS "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2012-08-13 09:38 -0800

csiph-web