VirtualBox

Ticket #2887 (closed defect: duplicate)

Opened 5 years ago

Last modified 5 years ago

HOST networking failure on Debian 4 amd64 host.

Reported by: quack Owned by:
Priority: major Component: network
Version: VirtualBox 2.1.0 Keywords:
Cc: Guest type: other
Host type: Linux

Description

HOSTIF networking appears not to be working using vbox 2.1.0 on Debian 4 amd64 using internet routeable IPs. I'm using networking which has a netmask of 255.255.240.0 and the gateway is located at x.y.z.1 while my IPs are all x.y.a.b - x.y.c.d (far away from each other, but whithin the netmask). The guest OS is assigned it's IP statically, so is the host. The IPs are tested to work in the host. OpenBSD and Linux guests both have this problem - so that rules out a specific OS problem. Attaching vbox.log from linux guest.

Attachments

vbox.log Download (31.7 KB) - added by quack 5 years ago.
VBox.log from linux guest.

Change History

Changed 5 years ago by quack

VBox.log from linux guest.

comment:1 Changed 5 years ago by bartus-h

I have the same problem on a hetzner.de dedicated server. I have a public IP, and an extra public subnet. The guests can't reach the gateway, and the gateway can't ping the guest. In NAT mode the internet is reachable.

Here is some extra information:

VBoxManage -v:
2.1.0r41146

uname -a:
Linux Debian-40-etch-64-minimal 2.6.18-6-amd64 #1 SMP Wed Oct 15 10:07:11 UTC 2008 86_64 GNU/Linux

I'd be happy to supply some more, and do some tests.

Regards,

Bart Habernickel

comment:2 in reply to: ↑ description Changed 5 years ago by bartus-h

Sorry, I posted this in the wrong place earlier...

I have the same problem on a hetzner.de dedicated server. I have a public IP, and an extra public subnet. The guests can't reach the gateway, and the gateway can't ping the guest. In NAT mode the internet is reachable.

Here is some extra information:

VBoxManage -v:
2.1.0r41146

uname -a:
Linux Debian-40-etch-64-minimal 2.6.18-6-amd64 #1 SMP Wed Oct 15 10:07:11 UTC 2008 86_64 GNU/Linux

I'd be happy to supply some more, and do some tests.

Regards,

Bart Habernickel

comment:3 follow-up: ↓ 4 Changed 5 years ago by frank

Please could you have a look at #2827 and test the suggested patch to rule out this problem?

comment:4 in reply to: ↑ 3 Changed 5 years ago by bartus-h

Replying to frank:

Please could you have a look at #2827 and test the suggested patch to rule out this problem?

Yes, I'm sorry for not mentioning this, but that did fix the problem. My system is running perfectly now, and I'more than happy to have migrated from VMware Server! I love the RDP system!

Thanx for replying

comment:5 follow-up: ↓ 6 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

Thanks for the feedback. I will close this one as duplicate then.

comment:6 in reply to: ↑ 5 Changed 5 years ago by bartus-h

Replying to frank:

Thanks for the feedback. I will close this one as duplicate then.

The description of the other problem has nothing to do with my symptoms. I didn't see any crashes or any malfunctions other than my packets not reaching the host and internet. It was by pure luck that I tried the patch (after 3 evenings of searching for a sollution). Maybe now people will find the solution by the reference in this thread :)

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use