Marc Haber <mh+vbox-users-community@...> writes: > > On Sat, Jun 04, 2011 at 12:52:01PM -0700, JD wrote: > > On 06/04/11 12:21, Marc Haber wrote: > > > When I try the exact same thing with an exactly identically configured > > > kernel 2.6.38.7, everything is fine. 2.6.39's bridges themselves seem > > > to be OK, a KVM guest can use the very same setup just fine. > > > > Did you check you firewall (/etc/sysconfig/iptables) > > to allow all traffic to the VM's subnet? > > No. It is clear that the packet filter cannot play in this game here > since > > - switching back to an older kernel (with the kernel being the _only_ > change) makes things work > - KVM with identically configured networking works. > > > Perhaps networking/firewall gurus have a more elegant way to set up > > these rules. > > Use ferm. > > Greetings > Marc > Same setup and problem here, but I found a fix: Add vboxnet0 to br0:
# brctl addif br0 vboxnet0 This resolved all my issues with the 2.6.39-* kernel and VirtualBox 4.0.8. Greetings, Christoph ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
