On Oct 9, 2012, at 8:26 AM, Marc Haber wrote: > With kernel 3.6.0 and kernel 3.6.1, however, NAT seems to be broken. I > don't see the answer packets coming in from the internet going out on > the bridge:
It's probably some silent dependency on a particular kernel option. VirtualBox seems bad about that. I'm running on a custom 3.6.1 kernel right now. Works fine in NAT or bridged. Host-only which is what I actually use isn't fully functional - I have to bring the vboxnet0 interface up by hand and configure it right after booting the first VM after a host reboot. I've tried removing some seemingly unnecessary stuff from the kernel, only to have the vbox* modules panic when I try to load them (which is absolutely no good if they try to load at boot). You might also need some newer user land networking utilities to support the newer kernel version. Cheers, -- Casey ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
