On Thu, Jun 11, 2009 at 12:26:20PM -0600, Peter Schow wrote: > On Thu, Jun 11, 2009 at 04:31:12PM +0200, Johannes Kastl wrote: > > I would say that depends on which way of networking you chose: Host > > interface, Nat, ... > > "Host Interface" seems to have been removed from the Virtual Box > vocabulary. The guest networking choices are now: > > - None > - NAT > - Bridged networking > - Internal networking > - Host-only networking > > Since Nico mentioned that he is using "vboxnet0", I'm assuming that > he's using Host-only networking.
Actually, I hadn't been, but it's what I had wanted. And... on OpenSolaris 2009.06 NWAM and vbox still fight each other. Specifically: - while VirtualBox does configure vboxnet0 correctly, it ends up not being up - if I then ifconfig vboxnet0 up, then NWAM will take it down and reset its configuration One workaround is to stop nwamd while I'm using VirtualBox. That's not great. Another workaround is to not use NWAM. That at least is reasonable since I have a very hacked version of Darren Moffat's netprof utility that I could live with. But I would prefer if NWAM and VirtualBox could live with each other. Incidentally, this is now on OpenSolaris 2009.06 (snv_111b) and VirtualBox 2.2.4. Nico -- _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
