If you're using VirtualBox 2.2.4, you can use Host-Only networking. It creates an internal network that you can use to communicate between your host and guest. You set that option the same place you set bridging. I do this regularly and it works well.
It seems that in the VirtualBox 3.X series, Host-Only networking requires an external network to work (at least that the case for Mac hosts). So, no help there. Maybe they'll fix the bug soon. On Tue, Aug 04, 2009 at 04:00:49PM +0200, Jochen Wiedmann wrote: > Hi, > > the subject may sound silly, but that's basically what I need. > > I have Virtualbox installed on a laptop. Usually, the laptop is > connected to an ethernet, when everything works fine. However, when > I'm on travel, it is not. In other words, from time to time eth0 (my > ethernet interface) is not available. As my box is configured for > bridging on eth0, that means that no network is available. (The actual > reason might be, that there is no DHCP server available, but be that > as it may.) > > An alternative would of course be NAT. However, my most important > network client (Nortel Contivity, a VPN client) doesn't work well with > NAT: I need bridging. > > Any ideas, what I might do? > > Thanks, > > Jochen > > -- > Base64 decoding, 300% faster than sun.misc.BASE64Decoder: > http://archive.netbsd.se/?ml=commons-dev&a=2008-05&t=7522166 > > _______________________________________________ > vbox-users mailing list > vbox-users@virtualbox.org > http://vbox.innotek.de/mailman/listinfo/vbox-users -- Ken Preslan <k...@preslan.org> _______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
