|
From: Henry N. <Hen...@ar...> - 2004-08-09 19:11:24
|
Dustin Webb wrote: > After that subject you're probably asking yourself > "What does this guy want to do?" My problem seems > fairly simple and while I've heard that there is a > solution, I haven't found it. I want to be able to > communicate between the host OS (in this case ms > windows xp) and my coLinux OS via TCP/IP while the > host machine *isn't* connected to a network. So far my > experience has been, I unplug my box from the network > and XP unloads the network drivers. I've checked the > Wiki, spoken with a couple of people in IRC and have > been perusing the mailing list archives with no luck. > Can anyone offer any tips or point me towards the > appropriate documention? > > TIA from a first time poster, > Dustin > http://www.daemonmaker.net That's right. I'm also use coLinux without network. I'm not using bridging mode. If you have installed coLinux, you should have two network adapters: 1. real network and 2. colinux "TAP-Win32 Adapter V8 (coLinux)" I have renamed the coLinux TAP (in network connections) from LAN-Connection into "LAN colinux", so I can see which of these is the right LAN. Than give TAP driver a other network as your real network. Sample of my system Real network under XP: 1. LAN-Connection: 192.168.0.71 default gateway: 192.168.0.1 2. TAP coLinux: 192.168.4.200 Inside coLinux TAP driver: 192.168.4.10 default gateway: 192.168.4.200 Connection between coLinux and XP goes only over network 192.168.4.0 and never outside of my computer. (with and without real LAN connected) If I need connection from coLinux to computer outside of XP, I need some static routings and gateways in XP. Henry |