> 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
Hi Well, at least in the host system it does not matter to have both eth0 and eth1 routed to the gateway 192.168.1.254 If I'm connected by wireless eth1 then eth0 stays inactive, if for some reason wireless gets disconnected or unavailable just connect the cable to eth0 and my internet keeps working as if nothing happened. In fact there's a strange issue, not bad but strange, with my both interfaces, let's say eth0:192.168.1.11(rj45) and eth1:192.168.1.12(wifi) If I ping them from a third party host 192.168.1.x BOTH of them send reply no matter if am connected by wire or wifi, as if they were connected simultaneously... I guess that is for some internal routing... Example: If connected by wireless 192.168.1.12 and from a third party host send a ping to the wired interface 192.168.1.11 it replies using the wireless interface! so no matter which medium is connected, both of them respond by the active one. This is not really a problem, in fact I like it since no matter how the computer is connected or if I change from wifi to cable, the connection stays active transparently as if nothing happened... Would it be a problem? Anyway will try to remove the eth0 routing and keep just the eth1 to see what happen... Am beginning to think that it will be better to leave NAT and services accessibe just in host<-guest direction, anyway the host or other host in the network rarely will access the guest, or create two virtual machines sharing a same disk image, one usinga NAT and other using Host Image, and just change WinXP guest IP configuration when required... Thanks for your patience _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
