virtualbox.org

Hi all,


we are using OpenVPN with a bridged setup inside a VirtualBox Guest. This works fine in 2.0.6 with host interface and a bridge setup on the host for this purpose. However, with the new host interface implementation in 2.1.0, this setup fails, no matter where I attach the guest to (both old style bridging and using a dedicated network interface do not work).

I've opened a ticket for this issue (#2900), however, I'd like to hear if others are having similar problems. Testing more intensively with tcpdump on all nodes, it seems that there is a significant delay (up to minutes), but most packets reach their destination after some time. Sometimes, they get completely lost too.. I'm not sure what causes this behavior as I am not 100% sure how the new vboxnetflt code actually works and wether it is compatible with a layer 2 bridge in the guest.

As for now, we stay at 2.0.6 until the problem is solved.


Thanks in advance for any help,


Chris

I just upgraded to 2.1. I run ubuntu hardy 64, had taps working fine and upgraded specifically for the 'improved' host interface support.

Funny thing is, I can ping and dns resolves all day long, but I cannot actually browse samba shares. I can map drives, but cannot view the content.

virtual folders or shared folders (whatever) work fine.

I hope this gets fixed.

Funny thing is, I can ping and dns resolves all day long, but I cannot actually browse samba shares. I can map drives, but cannot view the content.

Yep, I can confirm that ping'ing actually works without any problems... I wasn't able to establish any ssh connection or other TCP stuff... when testing with netcat, I had also tcp packets arriving through the VPN, but most of them were heavily delayed and some of it got lost on the way it seemed...