|
From: Dustin W. <dus...@ya...> - 2004-08-06 17:35:07
|
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 |
|
From: Tim H. <ti...@br...> - 2004-08-06 18:33:53
|
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? > http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q239/9/24.asp&NoWebContent=1 > TIA from a first time poster, > Dustin > http://www.daemonmaker.net > > |
|
From: Dustin W. <dus...@ya...> - 2004-08-06 21:21:43
|
--- Tim Hunter <ti...@br...> wrote: > 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? > > > > http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q239/9/24.asp&NoWebContent=1 Looked promising, but unfortunately it did not work. XP still unloaded the drivers. Dustin http://www.daemonmaker.net |
|
From: peter g. <plu...@p1...> - 2004-08-06 19:01:22
|
if you are using winpcap based netwokring and want to use it with the network unplugged you will need to disable media sense on your network card > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On Behalf Of Dustin > Webb > Sent: 06 August 2004 18:35 > To: col...@li... > Subject: [coLinux-users] LANless Networking between host and coLinux > > > 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 > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004 |
|
From: Dustin W. <dus...@ya...> - 2004-08-06 21:42:06
|
--- peter green <plu...@p1...> wrote: > if you are using winpcap based netwokring and want > to use it with the network unplugged you will need to > disable media sense on your network card I should have mentioned that I looked for this option in the configuration of my network card but it's not available. It is available on the TAP interface but I haven't been able to get my coLinux OS to speak with my host OS through the TAP interface. I adjusted the network element of the configuration file such that type="tap" and assigned the TAP interface a static ip, but it didn't work. I'm not really sure what I am doing wrong with that configuration. Any other thoughts? Thanks, Dustin http://www.daemonmaker.net |
|
From: Martin K. <ka...@po...> - 2004-08-07 13:12:56
|
Hi Dustin, did you tried to install Microsoft Loopback device? if you configure this the same way as your ethernet device you should be able to get it working. you can't have two devices on same network so if you have just disabled your lan you have to use another one, e.g.: LAN IP: 192.168.0.2 Mask:255.255.255.0 LoopBack: 192.168.1.2 Mask:255.255.255.0 and than you have to change your config to something like this: <network index="0" type="bridged" name="Loopback Connection" /> and you have to configure your linux to setup eth0 in 192.168.1.x network. e.g. (using debian): /etc/network/interfaces: .... iface eth0 inet static address 192.168.1.1 netmask 255.255.255.0 but i would prefer to use TAP - seems to be faster. Regards, Martin Dustin Webb wrote: > Any other > thoughts? |
|
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 |