bridged network issue with 2.2

[hamelg]

Hello,

I upgraded to 2.2. Now, bridged network connections between host and windows or Linux guests behave badly : file copies over network with scp are very slow (15Kb/s), lots of windows errors when using samba ...

Nat network mode is working normally.

To fix this issue, I must disable gso (global segmentation offload) feature of my host nic.
The host nic is a "Broadcom Corporation NetXtreme BCM5782 Gigabit Ethernet" and my linux kernel is 2.6.29.

Is anyone else having this problem ?

Regards

[ESP]

Hello,

I have a similar Problem with Samba since upgrading to VBox 2.2.
Host System is Windows XP, Samba is running in an openSUSE guest with Kernel 2.6.27.21-0.1, bridged-network connection.
When I copy or move files from Windows to the Samba-Share, the guest system freezes. Most of the time a restart of the guest fixes it, but the first attempt normally failes.

[Perryg]

I have been seeing a bit of this here. Try this for me. I don't know if it will help or not but set up the network in VBox to use the second adapter. Leave the information that you have in the first adapter just uncheck it. Do your tests and let me know.

[hamelg]

Try this for me. I don't know if it will help or not but set up the network in VBox to use the second adapter. Leave the information that you have in the first adapter just uncheck it. Do your tests and let me know.

The same goes for the second adapter.
I've tried to change the guest nic type for intel pro1000, again the same behavior.

I don't know if it is a kernel issue or a virtualbox bug because I upgraded both at the same time. To be sure, I must downgrade virtualbox to 2.1

Any other ideas ?

[skuda]

I have the same problem described here with version 2.2.2 but i have it from version 2.2, any workaround for this other than downgrade version?

[nmvega]

Interesting because I *just now* posted a detailed problem description, seemingly of the same problem.
Here is the link, in case it is useful to add detail to the issue:

http://forums.virtualbox.org/viewtopic.php?f=7&t=17712

Subject: File transfers (ftp/scp) btwn Linux VBox host and XP VM slow

[burghj]

I upgraded to 2.2. Now, bridged network connections between host and windows or Linux guests behave badly : file copies over network with scp are very slow (15Kb/s), lots of windows errors when using samba ...

To fix this issue, I must disable gso (global segmentation offload) feature of my host nic.
The host nic is a "Broadcom Corporation NetXtreme BCM5782 Gigabit Ethernet" and my linux kernel is 2.6.29.

This looks like the same problem that I reported in http://forums.virtualbox.org/viewtopic.php?f=7&t=16988
The thread was "locked" by some "operator" as being unsuitable for the forum.

But you have found the essential point yourself, namely that it has something to do with the gso feature in the linux kernel. With this information it is not difficult to google a redhat bugzilla entry https://bugzilla.redhat.com/show_bug.cgi?id=490266
where the whole problem is discussed, explained and solved.

It was/is a bug in the linux kernel 2.6.29 which was triggered by the tun driver (or perhaps the vbox netfilter in our cases) in connection with nic drivers that use that gso feature.

The (one-line) patch is now in the kernel sources since 2.6.29.2.

So we have various solutions now:
1) A workaround is to turn off the "segmentation offload" feature for the nic as you did already (ethtool ethn -K tso off seems to do the trick).
2) Add the one-line patch to your kernel sources yourself.
3) Use a kernel version from 2.6.29.2 up.

I'll try #2 myself for my system next week and report the results here.

JRO

[burghj]

So we have various solutions now:
1) A workaround is to turn off the "segmentation offload" feature for the nic as you did already (ethtool -K ethn tso off seems to do the trick).
2) Add the one-line patch to your kernel sources yourself.
3) Use a kernel version from 2.6.29.2 up.

I'll try #2 myself for my system next week and report the results here.

JRO

I have tested this now on my system and the network connections between host and guest work fine again.

JRO

[chika.tambun]

I have been seeing a bit of this here. Try this for me. I don't know if it will help or not but set up the network in VBox to use the second adapter. Leave the information that you have in the first adapter just uncheck it. Do your tests and let me know.

even till now i don't know exactly abt host interface/ bridging/ NAT
but it works when i setup ipaddress by using second adapter with intel* adapter with NAT
and first adapter set to host interface

N it works