[Pkg-virtualbox-devel] Bug#464574: Bug#464574: virtualbox-ose: No network in

[Emilio Jesús Gallego Arias]

Dear Mr. Meskes, thanks for your prompt response.

Michael Meskes <meskes at debian.org> writes:

>> I was successfully running virtualbox in Etch, but last week I upgraded
>
> Which package did you use on Etch?

My upgrade process went from 1.5.2-dfsg2-4~bpo40+1 -> 1.5.2-dfsg2-7 ->
1.5.4-dfsg-4

Umm, interesting, I downgraded back to 1.5.2-dfsg2-7, and that doesn't
work. 1.5.2-dfsg2-4 and 1.5.2-dfsg2-4~bpo40+ neither work in Lenny. 

So the virtualbox upgrade didn't cause the bug, it must be something
else. Umm, the box seems to run perfectly, and I was running the 2.6.22
backported kernel in Etch, I have no idea what can be causing this. The
tun device seems up and running:

$ ls -l /dev/net/tun 
crw------- 1 root root 10, 200 2008-08-08 10:08 /dev/net/tun

I would be good to hear if other Lenny users are suffering the bug, I'll
ask a mate running Lenny to try.

>> to Lenny, and all my virtual machines have lost net connectivity.
>
> Do you use the default NAT setup or a bridged setup? What does you
> /etc/vbox/intercfaces file contain?

The default NAT setup. Should I try other?

$ cat /etc/vbox/interfaces
# Linux static host networking interface configuration
#
# <interface> <user> <bridge>
# vbox0 guest br0

>> I can reproduce it with an Ubuntu live CD for the matter.
>
> Does this mean creating a new VM with that live CD also has no network
> connectivity?

Yes

>> $ ping $ANY_OTHER_IP
>> 100% packet loss
>
> This doesn't work for me either out of the box. How about some other
> ways to connect, e.g. tcptraceroute or a webbrowser? 

No way to get past the default gateway.

By the way, I lend a host with gutsy and the machines work, version
1.5.0-dfsg2-1ubuntu3.

But as I said, I think the problem is not in VirtualBox but in the way
it interacts with some Lenny subsystem.

Thanks for your work,

Emilio