Page 1 of 1

DHCP is not working with HIF Networking option

Posted: 5. Aug 2008, 18:38
by Sushilkar
I am new-bie in this HIF networking option with VBox. Please help me to out to configure this.

This is what i am trying to do:-

B4 that let me declare my guest and host details.

Host machine : Redhat EL 4 AS U2
Guest Machine : Not yet installed would like to load RHEL 4 AS U6

I have pointed the CD-ROM of my Virtual Box to use the 1st Disk ISO of RHEL AS U6. And I wish to carry out the installation from NFS server. Hence I have created a bridge (br0) with the interfaces (eth0 and vbox). But while carrying out the installation, i have selected the option 'ask method', however it is failing to get a DHCP IP address for vbox interface from local lan which bridge(eth0) is connected. I tried listening to VBOX interface, i could see a discover message but bridge is not passing that to my LAN side.

Here is the snippet from my box

Code: Select all

[root@mypc ~]# ifconfig
br0       Link encap:Ethernet  HWaddr 00:E0:81:5F:01:B9
          inet addr:192.168.1.250  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2ff:d0ff:fe8a:80bb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:63544 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83538 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3135881 (2.9 MiB)  TX bytes:68683836 (65.5 MiB)

eth0      Link encap:Ethernet  HWaddr 00:E0:81:5F:01:B9
          inet6 addr: fe80::2e0:81ff:fe5f:1b9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:63481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83170 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4408852 (4.2 MiB)  TX bytes:69154914 (65.9 MiB)
          Interrupt:209

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:64114097 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64114097 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3093127966 (2.8 GiB)  TX bytes:3093127966 (2.8 GiB)

vbox0     Link encap:Ethernet  HWaddr 00:FF:FD:DE:A9:48
          inet6 addr: fe80::2ff:fdff:fede:a948/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:8244 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:70 (70.0 b)

vbox1     Link encap:Ethernet  HWaddr 00:FF:A0:94:BA:3C
          inet6 addr: fe80::2ff:a0ff:fe94:ba3c/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:5 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@mypc ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.00e0815f01b9       no              eth0
                                                        vbox0


Any help will be appreciated

Thanks,
Sushil

Modedit: Added code block for readability.

Posted: 5. Aug 2008, 19:31
by Sasquatch
What LAN adapter did you choose for the Guest? If it's the PCNet, try the Intel one. As I have a bridge that functions just fine with the Intel/Pro1000MT adapter, I don't see why it wouldn't work.

@Sasquatch

Posted: 6. Aug 2008, 11:07
by Sushilkar
Thanks Mr. sasquatch.

Earlier I was using the Intel PRO/1000 T Server (82543GC). Before using this as my Guest's network card I myself had tried with the PCNet. So i thought of trying with another one. But over looked into it, so i thought i am installing a server machine OS, then why should i select Desktop named network card. That delayed my process. Any way thanks for your response. Your suggestion made me to check with Intel PRO/1000MT Desktop (82540EM) interface and found to be working fine.



Thanks,
Sushil :D