Page 1 of 1

problem with HIF

Posted: 7. Jun 2008, 01:41
by czk
I set up HIF as the document 6.7.1.1 said.
br0 address 192.168.1.2, gateway 192.168.1.1
guest address 192.168.1.3
in guest, i can ping 192.168.1.2, but cannot ping 192.168.1.1, why?

I'm using virtualbox 1.6.2 under ubuntu 8.04

Posted: 7. Jun 2008, 02:28
by Sasquatch
Did you set all the options correct, including gateway for the Guest? And of course added the interfaces to the bridge. Can you post your complete interface settings of both the VM and the Host system?

Posted: 7. Jun 2008, 02:38
by czk
interface of host:
auto lo
iface lo inet loopback

auto br0
iface br0 inet dhcp
bridge_ports wlan0

run the following to add vbox0 to br0:
sudo VBoxAddIF vbox0 $USER br0

check if bridge is ok:
$brctl show
bridge name bridge id STP enabled interfaces
br0 8000.001302c07559 no wlan0
vbox0

$ ifconfig br0
br0 Link encap:Ethernet HWaddr 00:13:02:c0:75:59
inet addr:192.168.1.2 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::213:2ff:fec0:7559/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1


$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0




in client:
Description . . . . . . . . . . . : Intel(R) PRO/1000 T Server Adapter #
2
Physical Address. . . . . . . . . : 08-00-27-EA-22-9F
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=1ms TTL=64
Reply from 192.168.1.2: bytes=32 time=1ms TTL=64
Reply from 192.168.1.2: bytes=32 time=1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Posted: 7. Jun 2008, 02:44
by Sasquatch
Ah, now we see. You want to bridge your wireless. That is not possibe, because bridge_utils does not have any wireless extensions. If you leave it for a couple of minutes, I think your host wireless won't work either. At least that was what I had when I treid it. There is a work around using some kind of internet sharing involving iptables and masquerading. I thought there was a topic about wireless bridging here somewhere, but I'm certain you can find more about this subject on Google.

Posted: 7. Jun 2008, 03:08
by czk
I see, thank you