When using linux guests, networking breaks in windows

[wojciechka]

Hi,

I have come across the same problem - Windows 8 x64, Realtek PCIe GBE Family Controller.

I tried to change network card settings (such as TX/RX offload options), but that did not change anything. My network card is "Realtek PCIe GBE Family Controller" (RTL8168) so I do not suspect this to be a driver-specific issue.

A possible workaround is to create a network bridge - I noticed it worked fine for me since I created the bridge. I also have an RTL8139 plugged in, so the bridge worked.

However, for some reason, creating the bridge caused the sleep not to work properly.

Did you get to resolve the issue or found any reasonable explanation for this?

[Stragulus]

The problem persisted until I lost my laptop a week ago. I've had all the virtualbox upgrades since then, none of which made any difference.

[dahoo]

As far as my investigation goes, the bridged network driver seems to be the problem causing a route loop on the network adapter, after i unchecked it in my network adapters settings, the loop is gone.

but if the guest os uses bridged network, i later need to delete the network of the guest-> check virtualbox bridged network driver in the windows network adapter settings ->add bridge network for the guest back again. now both the guest and hosting windows machine are fine.

[noteirak]

The pings in the CLI immediately stop coming in and all time out.

I lost track of this topic since you gave this new info along with the screenshot, but I must make this clear : you gave miss-leading information all along.
You clearly stated that the ping timed out, and I trusted you gave the exact error that was given to you by the system - isn't that how troubleshooting goes?

But actually, the error was : TTL expired in transit - which means one thing and one thing only : the ping went through so many routing network entities that if failed due to the limit set (which is between 64 and 128). This changes everything in the troubleshooting logic!.
Have you given the exact message from the start, I could have suggested a host issue.

What I am trying to say here is this : Be precise in your reports and ALWAYS give verbatim error messages. Do not change them, not even the layout. Give them exactly as they are, as they show, with what you did before and after. You had it almost all good, except for the error message.

That being said, I am glad to see you solved your problem.

[Stragulus]

O.t.o.h. you could expect that unless you get clear screenshots/text dumps, people in general are not very good at stating things exactly. To err is human. And while I agree with your general statement, I feel you're a bit offensive about it. I have since switched my OS'es around so that debian is the host and windows is the guest, which incidentally also 'resolved' the issue.