virtualbox.org

Hello,

I did a full install of Fedora 9. By full, I mean *ALL* packages on the Fedora DVD.

I then installed VirtualBox-1.6.2_31466_fedora9-1.i586.rpm.

I then tried to follow section '6.7.1.3 Bridging on Redhat and Fedora hosts' in UserManual.pdf as follows:

1. Created /etc/sysconfig/network-scripts/ifcfg-br0 as follows:
DEVICE=br0
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes
# HWADDR=a

c:d:e:f
# DHCP_HOSTNAME=xyz
# DNS1=1.1.1.1
# DNS2=2.2.2.2
# NM_CONTROLLED=

2. Edited /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=a

c:d:e:f
ONBOOT=yes
DHCP_HOSTNAME=xyz
DNS1=1.1.1.1
DNS2=2.2.2.2
NM_CONTROLLED=
BRIDGE=br0

3. Restarted network service as follows:
service network restart

Now, at this point, I cannot even ping local machines on my subnet (that I could earlier), let alone being able to ping www.google.com !

I'm hearing some chatter on the Net that when you do a full install of Fedora, Xen comes along with it and that Xen installs virbr0. Could virbr0 be interfering with the above configuration? Would like to know how I can get Vbox to work with *and* without Xen.

I'm not a TCP/IP or Unix expert, so please be a little kind in your responses. I, eg, don't understand why br0 needs to have BOOTPROTO=dhcp when a bridge is never supposed to have its own IP address (which is what dhcp givse based on the HWADDR of the device).

uname -a
Linux xyz 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686 i686 i386 GNU/Linux

Many thanks in advance to any and all who can suggest a fix for this problem; I'm stuck for the last several hours, unable to proceed further!

/SD

The NetworkManager rpms get installed automatically, and it seems they override the standard network startup scripts. I have read that NetworkManager doesn't work well with bridges, so that may be the issue.

A simple way to try:
$ service NetworkManager stop
$ service network restart

If that brings up your bridge properly, then just disable NetworkManager and use the "old" standard network startup scripts

$ chkconfig NetworkManager off
$ chkconfig network on

fkelbe wrote:The NetworkManager rpms get installed automatically, and it seems they override the standard network startup scripts. I have read that NetworkManager doesn't work well with bridges, so that may be the issue.

A simple way to try:
$ service NetworkManager stop
$ service network restart

If that brings up your bridge properly, then just disable NetworkManager and use the "old" standard network startup scripts

$ chkconfig NetworkManager off
$ chkconfig network on

Thanks, the eth0 bridging part works now. Also, someone suggested on the Fedora forum that I name by bridge so that it comes after eth0 in alphabetical order... to avoid autostart problems. So, I have renamed my bridge to: vboxbr0.

However, now, I still cannot get host to guest networking to work.

The problems:
o Cannot ping host from guest.
o Cannot ping guest from host.

My WinXP guest shows an IP address and subnet mask of 0.0.0.0 ! (No wonder.)

My local sys admin tells me that DHCP has been enabled for my guest MAC address and that, most likely, I do not have the network 'card' of my guest properly set up.

Would appreciate if someone could suggest a solution fast, as I'm really stuck on this one.

Here's my host ifconfig output.

Code: Select all

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:11:5F:F0:52  
          inet6 addr: fe80::211:11ff:fe5f:f052/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:821409 errors:0 dropped:0 overruns:0 frame:0
          TX packets:241956 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:749511483 (714.7 MiB)  TX bytes:26529652 (25.3 MiB)

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:12853 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12853 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:666284 (650.6 KiB)  TX bytes:666284 (650.6 KiB)

vboxbr0   Link encap:Ethernet  HWaddr 00:11:11:5F:F0:52  
          inet addr:192.168.16.21  Bcast:192.168.19.255  Mask:255.255.252.0
          inet6 addr: fe80::211:11ff:fe5f:f052/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:406825 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162514 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:195399918 (186.3 MiB)  TX bytes:20121225 (19.1 MiB)

vbox0     Link encap:Ethernet  HWaddr 00:FF:3A:0F:B1:19  
          inet6 addr: fe80::2ff:3aff:fe0f:b119/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:146 errors:0 dropped:88039 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:17994 (17.5 KiB)  TX bytes:8760 (8.5 KiB)

virbr0    Link encap:Ethernet  HWaddr 5E:60:EE:49:22:2F  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::5c60:eeff:fe49:222f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:6549 (6.3 KiB)

$ brctl show
bridge name	bridge id		STP enabled	interfaces
vboxbr0		8000.0011115ff052	no		eth0
                 						      	vbox0
virbr0		8000.000000000000	yes

The guest ipconfig address is not interesting. The IP address and subnet are both 0.0.0.0. The gwy / dns addresses show correctly because I have specified them manually in my guest's DHCP configuration.

Hi !

I've the same problem

and haven't find any solution till now.

Just solved my problem, it was a firewall issue.
You may disable your firewall or trust the br0 device

AsM0DeUz wrote:Just solved my problem, it was a firewall issue.
You may disable your firewall or trust the br0 device

Thank you so much! It works now.

Request/suggestion to the Virtual Box team: Since the User Manual already talks about some basics Linux networking anyways, it may be helpful (to a lot of me types) if it could ALSO mention a line or two about firewall, esp for Fedora that by default comes with the highest possible security settings burnt in.

/SD

virtualbox.org

Can't get Fedora instructions to work.

Can't get Fedora instructions to work.

NetworkManager

Re: NetworkManager