From: Henry N. <Hen...@Ar...> - 2008-03-30 20:29:31
|
Henry Nestler wrote: > Mike wrote: >> OK the scenario would than be: >> (for simplicity lets forget the host->guest connection for now) >> >> Internet Router: 192.168.2.254 >> >> Colinux: >> eth0: (taptun 10.0.1.1 255.255.255.0 10.0.1.255 gw 10.0.1.2) >> >> Host: >> wtap0 (WinTAP 10.0.1.2 255.255.255.0 10.0.1.255 gw 192.168.2.254) >> phys (Wifi 192.168.2.23 255.255.255.0 192.168.2.255 gw 192.168.2.254) >> >> +---------------------+ +-------------------------+ >> | Colinux guest | | WinXP host | +-----+ >> | eth0 +<------>+ wtap0 phys +<--->+lan >> | | ^ | +------>???<------+ | ^ +-----+ >> +---------------------+ | +-------------------------+ | >> | | >> 10.0.1.0 192.168.2.0 >> network network >> >> Question now is how to make sure the wtap0 forwards all communication to phys >> and vice versa? > > This type of forwarding is named "bridge". > > I'm prefer Windows bridge way. That I have tested with cable networks. > http://colinux.wikia.com/wiki/Network#TAP_with_Windows_Software_Bridge > > The other way is Internet Connection Sharing (ICS). > This is perhaps the better way for WLAN. > http://colinux.wikia.com/wiki/Network#Internet_Connection_Sharing_.28ICS.29 > "Networking" in > http://www.ibm.com/developerworks/library/l-virtualization-colinux/ > Think this description for ICS is better: http://colinux.wikia.com/wiki/Getting_Started_with_coLinux_-_Long_manual#Setting_up_networking_with_TAP-Win32_and_ICS -- Henry N. |