Simple bridging tutorial for ubuntu required.
-
unabatedshagie
- Posts: 5
- Joined: 28. Jun 2007, 20:56
Simple bridging tutorial for ubuntu required.
I'm running ubuntu gutsy and have virtualbox installed fom the repo.
I have windows installed in a guest machine.
What I would like to do is stream media from the windows guest to my xbox 360 using tversity.
Through what I have been able to find on the net it seems I have to set up a bridged connection between ubuntu and windows.
This is where I'm finding it hard to find information.
It seems like it's possible but as of posting this I have been unable to find anyone that has posted detailed info on how to do it.
I have read the virtualbox manual chapter on setting up bridging but if anything it has left me more confused than when I started.
Could some kind soul give me a hand in setting up bridging between the host and guest?
I have windows installed in a guest machine.
What I would like to do is stream media from the windows guest to my xbox 360 using tversity.
Through what I have been able to find on the net it seems I have to set up a bridged connection between ubuntu and windows.
This is where I'm finding it hard to find information.
It seems like it's possible but as of posting this I have been unable to find anyone that has posted detailed info on how to do it.
I have read the virtualbox manual chapter on setting up bridging but if anything it has left me more confused than when I started.
Could some kind soul give me a hand in setting up bridging between the host and guest?
-
unabatedshagie
- Posts: 5
- Joined: 28. Jun 2007, 20:56
-
stefan.becker
- Volunteer
- Posts: 7639
- Joined: 7. Jun 2007, 21:53
-
unabatedshagie
- Posts: 5
- Joined: 28. Jun 2007, 20:56
ok, fair enough.
I managed to find this which explains it in a slightly easier to read/understand format (for me anyway)
I followed it, installed bridge-utils and uml-utilities, changed the group, changed the network adapter to Host Interface and the interface name to tap0
Stopped the networking service, edited the file (changing bimma for my username and 10.10.10.60 to 192.168.0.2) changed the gateway to 192.168.0.1 and started networking service again.
This is the terminal output after I started networking up againI'm not sure if that's correct or not.
Started windows and there is a local area connection status icon in the notification area which states that there is limited or no connectivity.
192.168.0.2 is the ip address that I have set my router to assign to my linux machine, would that have any effect on what I'm trying to do?
I managed to find this which explains it in a slightly easier to read/understand format (for me anyway)
I followed it, installed bridge-utils and uml-utilities, changed the group, changed the network adapter to Host Interface and the interface name to tap0
Stopped the networking service, edited the file (changing bimma for my username and 10.10.10.60 to 192.168.0.2) changed the gateway to 192.168.0.1 and started networking service again.
This is the terminal output after I started networking up again
Code: Select all
alex@MysteryMachine:~$ sudo /etc/init.d/networking start
* Configuring network interfaces...
Set 'tap0' persistent and owned by uid 1000
net.ipv4.conf.tap0.proxy_arp = 1
Set 'tap1' persistent and owned by uid 1000
net.ipv4.conf.tap1.proxy_arp = 1
Set 'tap2' persistent and owned by uid 1000
net.ipv4.conf.tap2.proxy_arp = 1
Set 'tap3' persistent and owned by uid 1000
net.ipv4.conf.tap3.proxy_arp = 1
Set 'tap4' persistent and owned by uid 1000
net.ipv4.conf.tap4.proxy_arp = 1
Set 'tap5' persistent and owned by uid 1000
net.ipv4.conf.tap5.proxy_arp = 1
[ OK ]
alex@MysteryMachine:~$
Started windows and there is a local area connection status icon in the notification area which states that there is limited or no connectivity.
192.168.0.2 is the ip address that I have set my router to assign to my linux machine, would that have any effect on what I'm trying to do?
No, No, No.
That doesn't match your needs.
Please setup your /etc/network/interfaces like this:
Then execute these commands:<user> is your linux login name.
"My VM" is your virtual machine you will use for the brigde.
Now reboot your machine and give me the output of this command:
That doesn't match your needs.
Please setup your /etc/network/interfaces like this:
Code: Select all
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# setting up the bridge #######
auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
auto br0
iface br0 inet dhcp
bridge_ports eth0
# End setting up the bridge ###Code: Select all
$ sudo VBoxAddIF vbox0 <user> br0
$ VBoxManage modifyvm "My VM" -hostifdev1 vbox0"My VM" is your virtual machine you will use for the brigde.
Now reboot your machine and give me the output of this command:
Code: Select all
$ sudo ifconfig-
unabatedshagie
- Posts: 5
- Joined: 28. Jun 2007, 20:56
Ingo, thank you very much for the help.
The virtual machine can connect to the net at the same time as my main machine.
I'm about to try and get the virtual machine to connect to my xbox.
You wanted the output for the command ifconfig, well here it is.
The virtual machine can connect to the net at the same time as my main machine.
I'm about to try and get the virtual machine to connect to my xbox.
You wanted the output for the command ifconfig, well here it is.
Code: Select all
alex@MysteryMachine:~$ ifconfig
br0 Link encap:Ethernet HWaddr 00:18:F3:49:A9:3A
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe49:a93a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:774 (774.0 b) TX bytes:3835 (3.7 KB)
eth0 Link encap:Ethernet HWaddr 00:18:F3:49:A9:3A
inet6 addr: fe80::218:f3ff:fe49:a93a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:886 (886.0 b) TX bytes:3975 (3.8 KB)
Interrupt:16 Base address:0x4000
eth1 Link encap:Ethernet HWaddr 00:18:F3:49:AE:9C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xa000
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vbox0 Link encap:Ethernet HWaddr 00:FF:50:CF:42:C1
inet6 addr: fe80::2ff:50ff:fecf:42c1/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:6 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:15:AF:07:F8:DC
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-15-AF-07-F8-DC-00-00-00-00-00-00-00-00-00-00
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
alex@MysteryMachine:~$ I do not understand where this interfaces eth1, wlan0 and wmaster0 come from. They all have no IP address. But if they aren't part of the bridge don't worry about them. I suppose it's some initialized hardware e.g. wlan chip and firewire or so.
should only list two interfaces eth0 and vbox0.
Code: Select all
$ sudo brctl show-
unabatedshagie
- Posts: 5
- Joined: 28. Jun 2007, 20:56
-
carlosalvatore
- Posts: 2
- Joined: 21. May 2008, 17:15
Greetings, I'm having a similar problem. I want my virtualbox OS be able to share folders, and play multiplayer games (Starcraft).
I connect to the internet through a Gateway (2Wire), it assigns address via DHCP.
I'm hosting the VBox on Ubuntu Hardy 8.04, the guest OS is Windows XP SP2.
I've read this post and the docs, but nothing seams to work.
I've also tried to set the guest IP Address manually, then the Gateway sees the host, it recognize that there is a computer connected with a static IP address, but there is no connectivity at all.
This is my /etc/network/interfaces file
also:
The gateway acts like a Router-Modem with NAT, it is configured to provide DHCP address into the home network using this Address mask (195.165.0.x) with the subnet mask (255.255.255.0) The Gateway uses 195.165.0.1. So this is my default gateway to connect the internet.
This is the output when the network is restarted
The fact is when starting Windows XP (the guest OS) I can't get any IP address, so i don't know if I must set any static IP for it, 'cause in /etc/network/interfaces it's configured to use dhcp.
Any advice will be of help. Thank you very much. (Gracias very mucho!
)
Edit: I forgot to mention that the host OS has internet connection without problems, and the other (Windows) computers in the home network communicate each other without any problem, so the fact is that i want to add the VirtualBox to the network as a different entity (like it was another computer connected to the home network)
I connect to the internet through a Gateway (2Wire), it assigns address via DHCP.
I'm hosting the VBox on Ubuntu Hardy 8.04, the guest OS is Windows XP SP2.
I've read this post and the docs, but nothing seams to work.
I've also tried to set the guest IP Address manually, then the Gateway sees the host, it recognize that there is a computer connected with a static IP address, but there is no connectivity at all.
This is my /etc/network/interfaces file
Code: Select all
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
#iface eth0 inet dhcp
#
#auto tap0
#iface tap0 inet manual
#up ifconfig $IFACE 0.0.0.0 up
#down ifconfig $IFACE down
#tunctl_user carlosalvatore
#
auto br0
iface br0 inet dhcp
bridge_ports eth0Code: Select all
$ sudo brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0001803ae6ff no eth0
vbox0
Code: Select all
$ sudo ifconfig
br0 Link encap:Ethernet HWaddr 00:01:80:3a:e6:ff
inet addr:195.165.0.4 Bcast:195.165.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:80ff:fe3a:e6ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38823 errors:0 dropped:0 overruns:0 frame:0
TX packets:58000 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4989413 (4.7 MB) TX bytes:77187202 (73.6 MB)
eth0 Link encap:Ethernet HWaddr 00:01:80:3a:e6:ff
inet6 addr: fe80::201:80ff:fe3a:e6ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:181425 errors:0 dropped:0 overruns:0 frame:0
TX packets:266380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22707905 (21.6 MB) TX bytes:367811349 (350.7 MB)
Interrupt:11 Base address:0xd000
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:5630 errors:0 dropped:0 overruns:0 frame:0
TX packets:5630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:598055 (584.0 KB) TX bytes:598055 (584.0 KB)
vbox0 Link encap:Ethernet HWaddr 00:ff:db:b9:07:04
inet6 addr: fe80::2ff:dbff:feb9:704/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:95 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:15054 (14.7 KB) TX bytes:60 (60.0 B)This is the output when the network is restarted
Code: Select all
$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.br0.pid with pid 4483
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/br0/00:01:80:3a:e6:ff
Sending on LPF/br0/00:01:80:3a:e6:ff
Sending on Socket/fallback
DHCPRELEASE on br0 to 195.165.0.1 port 67
Waiting for br0 to get ready (MAXWAIT is 32 seconds).
There is already a pid file /var/run/dhclient.br0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/br0/00:01:80:3a:e6:ff
Sending on LPF/br0/00:01:80:3a:e6:ff
Sending on Socket/fallback
DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 8
DHCPOFFER of 195.165.0.4 from 195.165.0.1
DHCPREQUEST of 195.165.0.4 on br0 to 255.255.255.255 port 67
DHCPACK of 195.165.0.4 from 195.165.0.1
bound to 195.165.0.4 -- renewal in 1775 seconds.
[ OK ]
Any advice will be of help. Thank you very much. (Gracias very mucho!
Edit: I forgot to mention that the host OS has internet connection without problems, and the other (Windows) computers in the home network communicate each other without any problem, so the fact is that i want to add the VirtualBox to the network as a different entity (like it was another computer connected to the home network)
Carlos,
My setup is very similar to yours (host is hardy 8.04, guest XP pro, assuming vbox 1.6) and I am attempting to create the exact same setup. Like you, my host connects to my network just fine, but my XP guest cannot get an IP via DHCP.
My /etc/network/interfaces:
Which appears to work fine as the host does get the appropriate IP:
I started my DHCP server in debug mode, and I see the following: my guest sends a DHCPDISCOVER request, my DHCP server responds with an appropriate DHCPOFFER, and using wireshark on my host I see that the DHCPOFFER packets are making it to the host, but apparently the host is not passing those on via the br0/tap0 plumbing to the guest.
It appears as though I have this all configured properly. I followed the User Guide as well as another forum post where Ingo helped somebody in December with this problem, only they were on vbox 1.5 - http://forums.virtualbox.org/viewtopic. ... c&start=15).
At this point, it appears that somehow the hardy 8.04 bridge is not working as it should, or vbox is not passing the DHCPOFFERs back to the guest.
Can anyone offer any suggestions as to other things to try?
Thanks!
Bill
My setup is very similar to yours (host is hardy 8.04, guest XP pro, assuming vbox 1.6) and I am attempting to create the exact same setup. Like you, my host connects to my network just fine, but my XP guest cannot get an IP via DHCP.
My /etc/network/interfaces:
Code: Select all
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
auto tap0
iface tap0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
tunctl_user rkorb
auto br0
iface br0 inet dhcp
bridge_ports eth0 tap0
bridge_stp off
Code: Select all
8# ifconfig -a
br0 Link encap:Ethernet HWaddr 00:1d:09:4e:ae:6c
inet addr:192.168.1.113 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:9ff:fe4e:ae6c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16012 (15.6 KB) TX bytes:12225 (11.9 KB)
eth0 Link encap:Ethernet HWaddr 00:1d:09:4e:ae:6c
inet6 addr: fe80::21d:9ff:fe4e:ae6c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2968 errors:0 dropped:0 overruns:0 frame:0
TX packets:1866 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2389912 (2.2 MB) TX bytes:187930 (183.5 KB)
Interrupt:16
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:1990 errors:0 dropped:0 overruns:0 frame:0
TX packets:1990 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:99660 (97.3 KB) TX bytes:99660 (97.3 KB)
tap0 Link encap:Ethernet HWaddr 00:ff:8d:b1:eb:84
inet6 addr: fe80::2ff:8dff:feb1:eb84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:737 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:11764 (11.4 KB) TX bytes:120 (120.0 B)
It appears as though I have this all configured properly. I followed the User Guide as well as another forum post where Ingo helped somebody in December with this problem, only they were on vbox 1.5 - http://forums.virtualbox.org/viewtopic. ... c&start=15).
At this point, it appears that somehow the hardy 8.04 bridge is not working as it should, or vbox is not passing the DHCPOFFERs back to the guest.
Can anyone offer any suggestions as to other things to try?
Thanks!
Bill
Try this:korb wrote:Carlos,
My setup is very similar to yours (host is hardy 8.04, guest XP pro, assuming vbox 1.6) and I am attempting to create the exact same setup. Like you, my host connects to my network just fine, but my XP guest cannot get an IP via DHCP.
At this point, it appears that somehow the hardy 8.04 bridge is not working as it should, or vbox is not passing the DHCPOFFERs back to the guest.
Can anyone offer any suggestions as to other things to try?
Thanks!
Bill
/etc/network/interfaces:
Code: Select all
auto lo
iface lo inet loopback
auto br0
iface br0 inet dhcp
bridge_ports eth0
Code: Select all
sudo /etc/init.d/networking restartCode: Select all
sudo VBoxAddIF vbox0 Bill br0then attach vbox0 as HIF for your Windows Guest
(and don't forget in your Windows Guest to set DHCP client on)
-
carlosalvatore
- Posts: 2
- Joined: 21. May 2008, 17:15
In /etc/network/interfaces:gagarobu wrote:
Try this:
/etc/network/interfaces:Restart the networkCode: Select all
auto lo iface lo inet loopback auto br0 iface br0 inet dhcp bridge_ports eth0Add virtual networkcardCode: Select all
sudo /etc/init.d/networking restartBill is your usernameCode: Select all
sudo VBoxAddIF vbox0 Bill br0
then attach vbox0 as HIF for your Windows Guest
(and don't forget in your Windows Guest to set DHCP client on)
Did you mean
Code: Select all
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dchp
auto br0
iface br0 inet dhcp
bridge_ports eth0
Thank you
I agree somewhat with Carlos: I need to include configuration for eth0 in /etc/network/interfaces. That is because if I do not, Ubuntu (the host) automatically DHCPs for that interface, and both eth0 & br0 end up with the same IP address. When that happens, Ubuntu cannot contact other hosts, let alone the guest.
So I've decided to simplify, and remove the Ubuntu native items from the process. I deleted the uml-utilities package, deleted all of my tap interfaces, and started over.
Here is my current /etc/network/interfaces:
Note that I require that spanning tree be turned off, otherwise the broadcasts that result cause our corporate network to disable my switch port.
I created the vbox0 interface as directed in the vbox 1.6 User Manual (VBoxAddIF vbox0 rkorb br0).
My interfaces and bridge now look like this:
However, the Windoze guest is still unable to get a dynamic IP:
The Ubuntu account that is running vbox is named "rkorb", and it has the appropriate permissions on /dev/net/tun:
So although everything looks correct, clearly something is still amiss.
Any other thoughts?
Thanks,
Bill
So I've decided to simplify, and remove the Ubuntu native items from the process. I deleted the uml-utilities package, deleted all of my tap interfaces, and started over.
Here is my current /etc/network/interfaces:
Code: Select all
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_stp offI created the vbox0 interface as directed in the vbox 1.6 User Manual (VBoxAddIF vbox0 rkorb br0).
My interfaces and bridge now look like this:
Code: Select all
2# ifconfig -a
br0 Link encap:Ethernet HWaddr 00:1d:09:4e:ae:6c
inet addr:192.168.1.113 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:9ff:fe4e:ae6c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:414 errors:0 dropped:0 overruns:0 frame:0
TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:187114 (182.7 KB) TX bytes:45631 (44.5 KB)
eth0 Link encap:Ethernet HWaddr 00:1d:09:4e:ae:6c
inet6 addr: fe80::21d:9ff:fe4e:ae6c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:424 errors:0 dropped:0 overruns:0 frame:0
TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:187674 (183.2 KB) TX bytes:45631 (44.5 KB)
Interrupt:16
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:2066 errors:0 dropped:0 overruns:0 frame:0
TX packets:2066 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:103460 (101.0 KB) TX bytes:103460 (101.0 KB)
vbox0 Link encap:Ethernet HWaddr 00:ff:c6:e2:da:04
inet6 addr: fe80::2ff:c6ff:fee2:da04/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:162 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
3# brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.001d094eae6c no eth0
vbox0Code: Select all
C:\Documents and Settings\Administrator>ipconfig /renew
Windows IP Configuration
An error occurred while renewing interface Local Area Connection :
unable to contact your DHCP server. Request has timed out.
C:\Documents and Settings\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : maplapvbox-xp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-6F-2A-31
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.9.105
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :Code: Select all
4# ls -l /dev/net/tun
crw-rw---- 1 root vboxusers 10, 200 2008-05-15 19:09 /dev/net/tun
5# groups rkorb
adm dialout cdrom floppy audio dip video plugdev scanner lpadmin admin netdev powerdev sambashare vboxusersAny other thoughts?
Thanks,
Bill
have you try a dummy test?korb wrote:
Any other thoughts?
Thanks,
Bill
set an static ip address on your windows guest machine.
if your guest can connect to existing network, then the problem in your dhcp server (maybe your dhcp server set ip based on mac address, or else)
if your guest cannot connect to existing, then the problem is in vbox0 (HIF)