From: Robert C. <rw...@al...> - 2004-04-28 22:35:35
|
Hello all, I've installed the 20040421 snapshot and am trying to get networking working as described on this wiki page: http://colinux.org/wiki/index.php/coLinuxASAP I seem to be able to ping the IP address 192.168.0.40, but I cannot ping the Windows machine on which coLinux runs (Windows IP: 192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to the rest of the world. I'm looking for the simplest combination of a colinux snapshot (not necessarily 20040421) and network settings that will work, preferably using TAP. I have been sifting though the mailing list posts. While I have seen several "Thanks, I got it to work" posts, I haven't seen any summaries detailing what those steps were. I will summarize any success I have and post on a wiki page. Something like this: - download colinux-* snapshot - test with ping to windows machine then to the rest of the world - make these adjustments - test with ping to windows machine then to the rest of the world Thanks in advance for any pointers and advice. Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-04-28 22:41:13
|
On Wednesday, April 28, 2004, at 05:35 PM, Robert Citek wrote: > I've installed the 20040421 snapshot and am trying to get networking > working as described on this wiki page: > http://colinux.org/wiki/index.php/coLinuxASAP > > I seem to be able to ping the IP address 192.168.0.40, but I cannot > ping the Windows machine on which coLinux runs (Windows IP: > 192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to > the rest of the world. BTW, this is a Win2K machine. - Robert |
From: Sascha K. <ke...@gm...> - 2004-04-29 09:50:51
|
Robert Citek <rwcitek <at> alum.calberkeley.org> writes: > > On Wednesday, April 28, 2004, at 05:35 PM, Robert Citek wrote: > > I've installed the 20040421 snapshot and am trying to get networking > > working as described on this wiki page: > > http://colinux.org/wiki/index.php/coLinuxASAP > > > > I seem to be able to ping the IP address 192.168.0.40, but I cannot > > ping the Windows machine on which coLinux runs (Windows IP: > > 192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to > > the rest of the world. > > BTW, this is a Win2K machine. - Robert What's the IP address of the TAP-Win32 adapter (should be 192.168.0.1)? Is this adapter active (i.e. "cable plugged in")? If not, you have to configure TAP-Win32's "Media Status" to "Always Connected" instead of "Application Controlled". After this, you should be able to ping 192.168.0.1 from within coLinux and 192.168.0.40 from within Windows. Hope this helps, Sascha |
From: <ch...@to...> - 2004-04-29 11:32:44
|
After setting the TAP interface in windows to 192.168.0.1 like Sascha said. you need to share the connection provided by the physical NIC in windows. rt click on the (outside lan) interface. | properties | sharing tab | check "enable Internet Connection Sharing...." | ok. > Robert Citek <rwcitek <at> alum.calberkeley.org> writes: > >> >> On Wednesday, April 28, 2004, at 05:35 PM, Robert Citek wrote: >> > I've installed the 20040421 snapshot and am trying to get networking >> > working as described on this wiki page: >> > http://colinux.org/wiki/index.php/coLinuxASAP >> > >> > I seem to be able to ping the IP address 192.168.0.40, but I cannot >> > ping the Windows machine on which coLinux runs (Windows IP: >> > 192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to >> > the rest of the world. >> >> BTW, this is a Win2K machine. - Robert > > What's the IP address of the TAP-Win32 adapter (should be 192.168.0.1)? Is > this > adapter active (i.e. "cable plugged in")? If not, you have to configure > TAP-Win32's "Media Status" to "Always Connected" instead of "Application > Controlled". > > After this, you should be able to ping 192.168.0.1 from within coLinux and > 192.168.0.40 from within Windows. > > Hope this helps, > > Sascha > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Robert C. <rw...@al...> - 2004-04-29 13:55:47
|
Had a few minutes this morning to incorporate ideas from Sascha, Chris, and Evan (thanks). Notes at the bottom of this wiki page: http://cwelug.org/cgi-bin/wiki.cgi?CoLinux Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-04-30 06:34:15
|
On Thursday, Apr 29, 2004, at 08:55 US/Central, Robert Citek wrote: > Had a few minutes this morning to incorporate ideas from Sascha, > Chris, and Evan (thanks). Notes at the bottom of this wiki page: > http://cwelug.org/cgi-bin/wiki.cgi?CoLinux Got networking working once with the 20040421 snapshot. Will remove and reinstall colinux to see if I can reproduce the results, i.e. make sure I have not missed any steps. Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-04-30 08:10:06
|
On Friday, Apr 30, 2004, at 01:33 US/Central, Robert Citek wrote: > On Thursday, Apr 29, 2004, at 08:55 US/Central, Robert Citek wrote: >> Had a few minutes this morning to incorporate ideas from Sascha, >> Chris, and Evan (thanks). Notes at the bottom of this wiki page: >> http://cwelug.org/cgi-bin/wiki.cgi?CoLinux > > Got networking working once with the 20040421 snapshot. Will remove > and reinstall colinux to see if I can reproduce the results, i.e. make > sure I have not missed any steps. Tried to reproduce my results, but could not. Kept getting error when I tried to start the Internet Connection Sharing: "... the LAN connection selected as the private network is either not present, or is disconnected from the network. ..." The LAN connection is not only present but is very much connected, since I can ping Google via it. Oh, well. Got too much other stuff to work on. I'll try to get back to coLinux next week. Regards, - Robert |
From: Tomasz S. <to...@xi...> - 2004-04-30 08:27:14
|
Robert Citek wrote: > Tried to reproduce my results, but could not. Kept getting error when > I tried to start the Internet Connection Sharing: "... the LAN > connection selected as the private network is either not present, or > is disconnected from the network. ..." The LAN connection is not only > present but is very much connected, since I can ping Google via it. It complains about "LAN connection selected as the private network" - the TAP adapter. You need to start coLinux first and wait for it to connect to "the other side" of the TAP connection. P.S. You need to enter the name of the connection (the one you see in the Network Connections window) in the config XML file. For example I named mine "coLinux Network Adapter" and have: <network index="0" ... name="coLinux Network Adapter" /> in the default.colinux.xml file. Hope this helps. :-) -- Tomasz Sterna JID: sm...@ch... |
From: Robert C. <rw...@al...> - 2004-04-30 14:55:16
|
On Friday, Apr 30, 2004, at 03:27 US/Central, Tomasz Sterna wrote: > It complains about "LAN connection selected as the private network" - > the TAP adapter. > You need to start coLinux first and wait for it to connect to "the > other side" of the TAP connection. So, the sequence should be: 1 - start colinux 2 - allow ICS on the real NIC 3 - change the TAP device to "always connected" Tried it. Yup. That worked - repeatedly. Thanks. Updated the wiki. See the bottom of this page: http://cwelug.org/cgi-bin/wiki.cgi?CoLinux Will copy to colinux wiki soon. > P.S. You need to enter the name of the connection (the one you see in > the Network Connections window) in the config XML file. > For example I named mine "coLinux Network Adapter" and have: > <network index="0" ... name="coLinux Network Adapter" /> > in the default.colinux.xml file. I called mine "TAP" to conform with the default .xml file. > Hope this helps. :-) Very much. I've been able to reproduce the steps to get coLinux 20040421 working with networking. Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-05-02 23:26:04
|
On Friday, Apr 30, 2004, at 09:01 US/Central, Robert Citek wrote: > Tried it. Yup. That worked - repeatedly. Thanks. Updated the wiki. > See the bottom of this page: > http://cwelug.org/cgi-bin/wiki.cgi?CoLinux > Will copy to colinux wiki soon. I was able to repeat the process with the colinux-20040429 snapshot. All works well. In fact, I can skip the step that renames the TAP device. Regards, - Robert |
From: Samuel L. <sa...@li...> - 2004-05-01 00:23:55
|
"Tomasz Sterna" <to...@xi...> wrote in message news:409...@xi...... > P.S. You need to enter the name of the connection (the one you see in > the Network Connections window) in the config XML file. > For example I named mine "coLinux Network Adapter" and have: > <network index="0" ... name="coLinux Network Adapter" /> > in the default.colinux.xml file. Are you sure; I thought it was the name of the adaptor as showin in properties, not the name of the connection. Sam |
From: Tomasz S. <to...@xi...> - 2004-05-01 20:55:39
|
Samuel Liddicott wrote: > Are you sure; I thought it was the name of the adaptor as showin in > properties, not the name of the connection. Yes, I'm sure. :-) I tried to setup it with the adapter driver name, like it is explained on the wiki pages - it dodn't work. When I entered the adapter name - it works. :-) -- smoku |
From: Evan D. <eda...@tj...> - 2004-04-29 12:20:34
|
One more thing I'll throw in that gave me a bit of trouble - at least in XP, you have to enable the TAP driver, let it show the "network disconnected" message, then run Colinux. It should change to connected when you run Colinux. ch...@to... wrote: >After setting the TAP interface in windows to 192.168.0.1 like Sascha said. >you need to share the connection provided by the physical NIC in windows. >rt click on the (outside lan) interface. | properties | sharing tab | >check "enable Internet Connection Sharing...." | ok. > > > >>Robert Citek <rwcitek <at> alum.calberkeley.org> writes: >> >> >> >>>On Wednesday, April 28, 2004, at 05:35 PM, Robert Citek wrote: >>> >>> >>>>I've installed the 20040421 snapshot and am trying to get networking >>>>working as described on this wiki page: >>>> http://colinux.org/wiki/index.php/coLinuxASAP >>>> >>>>I seem to be able to ping the IP address 192.168.0.40, but I cannot >>>>ping the Windows machine on which coLinux runs (Windows IP: >>>>192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to >>>>the rest of the world. >>>> >>>> >>>BTW, this is a Win2K machine. - Robert >>> >>> >>What's the IP address of the TAP-Win32 adapter (should be 192.168.0.1)? Is >>this >>adapter active (i.e. "cable plugged in")? If not, you have to configure >>TAP-Win32's "Media Status" to "Always Connected" instead of "Application >>Controlled". >> >>After this, you should be able to ping 192.168.0.1 from within coLinux and >>192.168.0.40 from within Windows. >> >>Hope this helps, >> >>Sascha >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: Oracle 10g >>Get certified on the hottest thing ever to hit the market... Oracle 10g. >>Take an Oracle 10g class now, and we'll give you the exam FREE. >>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >>_______________________________________________ >>coLinux-devel mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-devel >> >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: Oracle 10g >Get certified on the hottest thing ever to hit the market... Oracle 10g. >Take an Oracle 10g class now, and we'll give you the exam FREE. >http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
From: <ch...@to...> - 2004-04-29 17:30:54
|
good point. this applies to 2k as well. Run colinux so tap is connected then share the outside lan. ICS will complain if tap is disconnected. chris > One more thing I'll throw in that gave me a bit of trouble - at least in > XP, you have to enable the TAP driver, let it show the "network > disconnected" message, then run Colinux. It should change to connected > when you run Colinux. > > ch...@to... wrote: > >>After setting the TAP interface in windows to 192.168.0.1 like Sascha >> said. >>you need to share the connection provided by the physical NIC in windows. >>rt click on the (outside lan) interface. | properties | sharing tab | >>check "enable Internet Connection Sharing...." | ok. >> >> >> >>>Robert Citek <rwcitek <at> alum.calberkeley.org> writes: >>> >>> >>> >>>>On Wednesday, April 28, 2004, at 05:35 PM, Robert Citek wrote: >>>> >>>> >>>>>I've installed the 20040421 snapshot and am trying to get networking >>>>>working as described on this wiki page: >>>>> http://colinux.org/wiki/index.php/coLinuxASAP >>>>> >>>>>I seem to be able to ping the IP address 192.168.0.40, but I cannot >>>>>ping the Windows machine on which coLinux runs (Windows IP: >>>>>192.168.131.68; Windows gateway: 192.168.131.254) nor can I get out to >>>>>the rest of the world. >>>>> >>>>> >>>>BTW, this is a Win2K machine. - Robert >>>> >>>> >>>What's the IP address of the TAP-Win32 adapter (should be 192.168.0.1)? >>> Is >>>this >>>adapter active (i.e. "cable plugged in")? If not, you have to configure >>>TAP-Win32's "Media Status" to "Always Connected" instead of "Application >>>Controlled". >>> >>>After this, you should be able to ping 192.168.0.1 from within coLinux >>> and >>>192.168.0.40 from within Windows. >>> >>>Hope this helps, >>> >>>Sascha >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: Oracle 10g >>>Get certified on the hottest thing ever to hit the market... Oracle 10g. >>>Take an Oracle 10g class now, and we'll give you the exam FREE. >>>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >>>_______________________________________________ >>>coLinux-devel mailing list >>>coL...@li... >>>https://lists.sourceforge.net/lists/listinfo/colinux-devel >>> >>> >>> >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: Oracle 10g >>Get certified on the hottest thing ever to hit the market... Oracle 10g. >>Take an Oracle 10g class now, and we'll give you the exam FREE. >>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >>_______________________________________________ >>coLinux-devel mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-devel >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |