vbox0 has limited or no connectivity

[marty916]

I am running Ubuntu 8.04 AMD64 and need to use host interface since there is an error with nat. IP is set via DHCP.

I've read the manuals, wiki and forum but I cannot get it working.
I'm trying to run two xp boxes.

What I'm basically trying to do is use host interface instead of nat
to use the internet on the two virtual machines.

A method is discussed here http://www.virtualbox.org/ticket/1046 but
is not clear enough.

If someone can walk me through the steps.

Thanks

[Sasquatch]

Please read the VirtualBox FAQ before attempting a bridge. If you meet the requirements, read the Forum Posting Guide and give the proper information. E.g. what is the real purpose and why isn't NAT sufficient.

[marty916]

Thanks for the swift reply,

I've read through the faq's and posting guide.

This is the only reason I'm looking for an alternative.

http://www.virtualbox.org/ticket/1046
!!Assertion Failed!!
Expression: <NULL>
Location : /home/vbox/vbox-1.6/src/VBox/Devices/Network/slirp/tcp_subr.c(1341) VBoxU32PtrHashSlow
NAT pointer hash error. pv=00002aaab036c890 cpvHashUsed=321 cpvHashCollisions=198

Using nat on ubuntu 8.01 amd64 causes virtualbox 1.6.4 to crash
(buggy slirp engine)

[marty916]

Host : Ubuntu 8.01 AMD64
Guest : Windows XP 32bit
Connection Type: PPPoE


Have two xp machines that i need to use with host interface, need host and guests to have internet access.

[Norpan]

Hi!
I had the same case, then I found out that you can only bridge one interface with another (eth1-vbox0) so I am thinking what if you create two alias interface some how and then makes two bridges vbox0 and vbox1? Is that posible? like this: eth1:1-vbox0 and eth1:1-vbox1.

Aparantly wrong, sorry!

[marty916]

Hi!
I had the same case, then I found out that you can only bridge one interface with another (eth1-vbox0) so I am thinking what if you create two alias interface some how and then makes two bridges vbox0 and vbox1? Is that posible? like this: eth1:1-vbox0 and eth1:1-vbox1.

Thanks for the tip, I've tried with one and I still get no connectivity, when i add the bridge i lose internet access in ubuntu host immediately.

I followed the directions at http://home.nyc.rr.com/computertaijutsu/vboxbridge.html step by step and still cannot get a connection.

I have added another network card so I have eth0 and eth1. I tried with eth1 but as soon as I create a bridge I continue to lose internet access.


1) Hardware:
Dell XPS 600 Desktop
CPU : Intel Pentium 4 3.20 Ghz
RAM : 8GB ram

Software:
Host OS : Ubuntu Hardy 8.0.1 AMD64
Guest : Windows XP Pro 32Bit

------------------------------
* 2701HG-B Gateway
ATM Encapsulation : bridged llc
Connection Type: PPPoE
Public Routed Subinterface disabled
Public Proxied Subnet (NAT/Routed) disabled


my interfaces file

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

# The secondary network interface
auto eth1
iface eth1 inet dhcp

[Sasquatch]

A bridge can have more than two interfaces in them. I have a bridge with at least 3 interfaces, eth0, vbox0 and vbox1. Sometimes I even add vbox2 to it.

As stated in the link and FAQ, wireless bridges will not work, they cause the Host to lose all connectivity. Using parprouted should work as stated in the link above.

[marty916]

A bridge can have more than two interfaces in them. I have a bridge with at least 3 interfaces, eth0, vbox0 and vbox1. Sometimes I even add vbox2 to it.

As stated in the link and FAQ, wireless bridges will not work, they cause the Host to lose all connectivity. Using parprouted should work as stated in the link above.

Thanks for replying,

I tried that and it doesn't work for me, although I'm not trying anything wireless at this point.

Both eth0 and eth1 are physically connected/wired to my 2701HG-B Gateway.

All I want is for eth1 to use vbox0 and vbox1 within virtualbox with or without a bridge, all I need is internet access on these boxes, I tried Internet Connection Sharing with firestarter but it doesnt work.

The reason I'm doing this is because I can't use nat anymore since it crashes the machines a lot,

Ticket# 1046 - http://www.virtualbox.org/ticket/1046
This is a known problem with NAT on 64-bit hosts. The problem is that slirp (the NAT engine VirtualBox is using) is not 64-bit clean. Our hack to work around this problem is obviously not sufficient...

This is the only reason I want to use vbox0 and vbox1 host interface
with no wireless setup.


what setup should i use, Any suggestions?

Thanks

[marty916]

Ok I got it to work, I created a bridge, created the interfaces.

The only problem now is that I get the same ip address on host and guests, also vbox0, vbox1 and eth1 shows connection has limited or no connectivity.

Code: Select all

/etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

# The secondary network interface
auto eth1
iface eth1 inet manual

auto br0
iface br0 inet dhcp
    bridge_ports eth1 vbox0 vbox1

my ifconfig
-------------------------
br0       Link encap:Ethernet  HWaddr 00:00:e8:ef:63:7d  
          inet addr:192.168.1.136  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::200:e8ff:feef:637d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6060 (5.9 KB)  TX bytes:1152 (1.1 KB)

eth0      Link encap:Ethernet  HWaddr 00:14:22:32:d6:26  
          inet addr:192.168.1.65  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:fe32:d626/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3512 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2557 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3456919 (3.2 MB)  TX bytes:348078 (339.9 KB)
          Interrupt:23 Base address:0x6000 

eth1      Link encap:Ethernet  HWaddr 00:00:e8:ef:63:7d  
          inet6 addr: fe80::200:e8ff:feef:637d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3595 errors:0 dropped:0 overruns:0 frame:0
          TX packets:689 errors:0 dropped:0 overruns:0 carrier:0
          collisions:8 txqueuelen:1000 
          RX bytes:743756 (726.3 KB)  TX bytes:99309 (96.9 KB)
          Interrupt:19 Base address:0xdca0 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:64 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3580 (3.4 KB)  TX bytes:3580 (3.4 KB)

vbox0     Link encap:Ethernet  HWaddr 00:ff:ea:93:87:28  
          inet6 addr: fe80::2ff:eaff:fe93:8728/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:487 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vbox1     Link encap:Ethernet  HWaddr 00:ff:b4:ee:c6:24  
          inet6 addr: fe80::2ff:b4ff:feee:c624/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1014 errors:0 dropped:21 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:94847 (92.6 KB)  TX bytes:405895 (396.3 KB)