On Wed, Aug 27, 2008 at 1:42 PM, <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I am more confused than before. :-) >> >> I don't know if I will be able to help you but, if possible to >> you, could you post the output of >> route -n, ifconfig and brctl show br0, after you have applied all your >> configurations? >> >> Best regards, >> >> Cássio > > >> Hi, >> >> I am more confused than before. :-) >> >> I don't know if I will be able to help you but, if possible to >> you, could you post the output of >> route -n, ifconfig and brctl show br0, after you have applied all your >> configurations? > > Hehehe, I will include all information before and after making the bridge > and host interface, it may be large but I guess it is necesary... Note > that eth0 is wired and eth1 wireless, VirtualBox works exactly the same > way in both cases... > > CONFIGURATION BEFORE HOST INTERFACE > ----------------------------------- > > Note that it is currently working, am writting you this message over the > eth1 wireless connection. > >>>> ifconfig <<< > > eth0 Link encap:Ethernet HWaddr 00:c0:9f:98:64:b1 > inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0 > 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:16 Base address:0x3000 > > eth1 Link encap:Ethernet HWaddr 00:12:f0:50:c0:36 > inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::212:f0ff:fe50:c036/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24930 errors:0 dropped:0 overruns:0 frame:0 > TX packets:22755 errors:0 dropped:0 overruns:0 carrier:1 > collisions:0 txqueuelen:1000 > RX bytes:13615153 (12.9 MiB) TX bytes:5392502 (5.1 MiB) > Interrupt:18 Base address:0xe000 Memory:e0206000-e0206fff > > 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:215 errors:0 dropped:0 overruns:0 frame:0 > TX packets:215 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:6597 (6.4 KiB) TX bytes:6597 (6.4 KiB) > >>>> route <<< > > Destination Gateway Genmask Flags Metric Ref Use Iface > localnet * 255.255.255.0 U 0 0 0 eth1 > localnet * 255.255.255.0 U 0 0 0 eth0 > localnet * 255.255.255.0 U 0 0 0 eth1 > loopback * 255.0.0.0 U 0 0 0 lo > default gateway.2wire.n 0.0.0.0 UG 0 0 0 eth1 > default gateway.2wire.n 0.0.0.0 UG 1 0 0 eth0 > > > CONFIGURATION AFTER HOST INTERFACE > ---------------------------------- > > Here will lose connection and will be back in a minute after the process. > > # modprobe tun > # echo "1" > /proc/sys/net/ipv4/ip_forward > # brctl addbr br0 > # ifconfig eth1 0.0.0.0 > # brctl addif br0 eth1 > # ifconfig br0 192.168.1.12 netmask 255.255.255.0 mtu 1500 > # VBoxAddIF vbox0 alphaomega br0 > VirtualBox host networking interface creation utility, version 1.6.4 > (C) 2005-2007 Sun Microsystems, Inc. > All rights reserved. > > Creating the permanent host networking interface "vbox0" for user alphaomega. > > at this moment br0 does not appear in the routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface > localnet * 255.255.255.0 U 0 0 0 eth0 > localnet * 255.255.255.0 U 0 0 0 br0 > loopback * 255.0.0.0 U 0 0 0 lo > default gateway.2wire.n 0.0.0.0 UG 1 0 0 eth0 > > so I will do it by hand (same way as my wifi script but applied now to br0) > > # route add -net 192.168.1.0 netmask 255.255.255.0 dev br0 > # route add default gw 192.168.1.254 dev br0 > > at this point my internet connection is restablished in host and now it > appears br0 in the routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface > localnet * 255.255.255.0 U 0 0 0 br0 > localnet * 255.255.255.0 U 0 0 0 eth0 > localnet * 255.255.255.0 U 0 0 0 br0 > loopback * 255.0.0.0 U 0 0 0 lo > default gateway.2wire.n 0.0.0.0 UG 0 0 0 br0 > default gateway.2wire.n 0.0.0.0 UG 1 0 0 eth0 > >>>> ifconfig <<< > > br0 Link encap:Ethernet HWaddr 00:12:f0:50:c0:36 > inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::212:f0ff:fe50:c036/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:334 errors:0 dropped:0 overruns:0 frame:0 > TX packets:337 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:69638 (68.0 KiB) TX bytes:62952 (61.4 KiB) > > eth0 Link encap:Ethernet HWaddr 00:c0:9f:98:64:b1 > inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0 > 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:16 Base address:0x3000 > > eth1 Link encap:Ethernet HWaddr 00:12:f0:50:c0:36 > inet6 addr: fe80::212:f0ff:fe50:c036/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:726 errors:0 dropped:0 overruns:0 frame:0 > TX packets:632 errors:0 dropped:0 overruns:0 carrier:1 > collisions:0 txqueuelen:1000 > RX bytes:139457 (136.1 KiB) TX bytes:116963 (114.2 KiB) > Interrupt:18 Base address:0x4000 Memory:e0206000-e0206fff > > 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:421 errors:0 dropped:0 overruns:0 frame:0 > TX packets:421 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:23319 (22.7 KiB) TX bytes:23319 (22.7 KiB) > > vbox0 Link encap:Ethernet HWaddr 00:ff:27:b9:ec:01 > inet6 addr: fe80::2ff:27ff:feb9:ec01/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:58 overruns:0 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > >>>> running VirtualBox <<< > > Attached to: Host Interface > [x] Cable connected > Interface Name: vbox0 > > now the box is being started, I will change the TCP/IP configuration from > Automatic to manual and will assign > > Guest WinXP: > IP 192.168.1.13 (one after br0/eth1) > netmask 255.255.255.0 > gateway 192.168.1.254 (the router's IP / default gateway for eth#) > DNS... the same ones I always use > > then will restart the guest WinXP to ensure the network configuration is > updated... > > now will test connectivity... > > - ping works in both ways host<->guest except guest->192.168.1.254 > - windows shares work in both ways host(samba)<->guest(winxp) > - there's no connection to internet since 192.168.1.254 is inaccesible > > Routing table might be okay since I'm currently writting to you from the > host system =-) > > > Did you see something anormal in the configuration? > > > Thanks very much!!!
How are you dealing with two default routes? ( br0 and eth0 ) You have eth1 (wireless) and vbox(0) in the bridge br0. So, what is that eth0 in the same net as br0? What is connected to eth0? I don't know how bridge code will deal with the wireless interface, so I will consider that it will play ok. In my opinion, in your configuration, you must have a default route do 192.168.1.254 dev br0 and clarify what is the reason to have eth0 with the same net as br0. Except when using advanced routing (lartc.org) I think that two default routes will result in problems. I use my default route pointing to br0 and all my guests use the same default gw IP as the host system. I hope it helps you. Regards, Cásio _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
