Okay, so it works with the stock kernel when I don't load the module and don't start the vboxnet service on boot, but just manually load the vboxnetflt module when the system is up. Then I start virtualbox and the network works fine. Unfortunately there is no indication what kernel modules are needed. I think it needs at least netgraph and ng_ether. But obviously that's not enough since network still doesn't work with my custom kernel.
Oh, and then it regularly freezes my whole system after running for about 20 minutes and I have to do a hardware reset ... ;-) On 05/09/10 13:37, Anselm Strauss wrote: > Hi, > > I'm running VirtualBox 3.1.6 on FreeBSD 8.0 amd64. I loaded the vboxdrv > module on boot and started the vboxnet service. Then I set up an Ubuntu > 10.04 amd64 guest and configured one bridged network interface. But I > can't get an IP address from my DHCP server. When I check with tcpdump > on all hosts, the traffic goes out from the Ubuntu guest over the > FreeBSD host and arrives at my DHCP server. The replies come in on the > host system but are then somehow not forwarded to the guest. I never see > incoming traffic on the guest system. > > I tested this with the stock FreeBSD kernel and with both types bridged > and NAT networking. There is no firewall on the host system. > > Any ideas? > > Thanks, > Anselm _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
