Menu
▾
▴
colinux-users
|
From: John F. <J.P...@as...> - 2004-08-13 12:12:16
|
I have set up coLinux using 0.6.1 and the Fedora Core 1 distribution. I am using Tap and Internet Connection sharing. All this works well on two installations, one Windows XP and one Windows 2000. I also run vncserver and samba on the Fedora coLinux and can see these on the PC hosting coLinux. I would like to enable these services on another PC in the same workgroup as the host PC, and I have been unable to discover how to configure the routing in the host windows XP PC to do this. Example Real network ========== HOST PC: 192.168.123.2 (Windows XP) Another PC: 192.168.123.1 (Windows 95 OSR 2) Gateway: 192.168.123.254 coLinux Network ===== TAP Gateway 192.168.0.1 coLinux 192.168.0.40 ICS enabled on the Real network on the HOST PC. coLinux can ping to 192.168.123.1 the other PC cannot ping to 192.168.0.40 or 192.168.0.1 I think that one way to overcome this problem would be to enable a NAT service and allocate to the coLinux an IP number in the series of the real network. e.g. 192.168.123.40 <=> 192.168.0.40 The problem is that I cannot find out how to do this. There are a number of items in XP e.g. RRAS, netsh, route, which are just not intended for ordinary people to know about. We are expected to use tools which assume we want to do something different. I found this web site which suggests modification to the Regstry setting for IpEnableRouter and I have applied this to the XP computer but it is not the complete solution. http://www.wown.com/j_helmig/w2kprout.htm There is also some discussion of the problem at this page on the wiki http://www.colinux.org/wiki/index.php/StepByStepInXP Any help will be appreciated and I'll put the solution to this onto the wiki. John Fletcher ------------------------------------------------------------------- Dr John P. Fletcher Tel: (44) 121 359 3611 ext 4625 Chemical Engineering and Applied Chemistry (CEAC), School of Engineering and Applied Science (SEAS), Aston University, Fax: (44) 121 359 4094 Aston Triangle, Email: J.P...@as... BIRMINGHAM B4 7ET U.K. CEAC Web site http://www.ceac.aston.ac.uk/ |
|
From: baldyeti <e_...@ho...> - 2004-08-13 16:00:24
|
I'd guess whatever targets anything but 192.168.123.x is sent by the win95 box to the gateway. So it's the gateway which needs to be told that traffic to 192.168.1.x needs to go to the win2k machine. Check your gateway manual on how to add a route there. Alternatively, win95 might have a route.exe or equivalent command, with which you could override the default gateway for a particular IP range. |
|
From: John F. <J.P...@as...> - 2004-08-16 10:40:44
|
I have done some more testing on my routing problem. The solution on Windows XP has been to swap from Internet Connection Sharing to using the Windows XP bridging. When that is installed and the appropriate settings made for the external network, the coLinux "computer" is seen as part of the external network. This means that the IP settings for eth0 in the colinux change to those needed for the external network. e.g. in my case where the external network is 192.168.123.x then 192.168.123.40 is a valid choice for the colinux. I had become confused as I had not realised that there are two distinct ways of organising what is referred to as "Native Bridging" on the wiki page http://www.colinux.org/wiki/index.php/coLinuxNetworking (a) Native bridging using type="bridged" in the colinux configuration. (b) Native bridging using type="tap" in the colinux configuration and then using a Windows XP bridge. When I have set up type (b) and changed the IP number, I have been able to access the colinux using both Samba and VNC from the second computer on my network, which is what I wanted to do. Thank you for providing such a useful tool. Best wishes John Fletcher ------------------------------------------------------------------- Dr John P. Fletcher Tel: (44) 121 359 3611 ext 4625 Chemical Engineering and Applied Chemistry (CEAC), School of Engineering and Applied Science (SEAS), Aston University, Fax: (44) 121 359 4094 Aston Triangle, Email: J.P...@as... BIRMINGHAM B4 7ET U.K. CEAC Web site http://www.ceac.aston.ac.uk/ |
|
From: John F. <J.P...@as...> - 2004-08-13 16:14:33
|
To: col...@li... From: baldyeti <e_...@ho...> Organization: - Subject: [coLinux-users] Re: Routing problem to coLinux from other computers Date sent: Fri, 13 Aug 2004 17:48:27 +0200 > I'd guess whatever targets anything but 192.168.123.x is > sent by the win95 box to the gateway. So it's the gateway > which needs to be told that traffic to 192.168.1.x needs > to go to the win2k machine. Check your gateway manual on > how to add a route there. Alternatively, win95 might have > a route.exe or equivalent command, with which you could > override the default gateway for a particular IP range. > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save > 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ coLinux-users mailing > list coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > I've done "route print" on the Win95 and even done a "route add" on it using examples from "Practical TCP/IP" Niall Mansfield. I am wondering if I am wrong to use ICS at all. Should I be using coLinux bridge instead of TAP? If so, should I use WinXP's bridge as well? One of the problems is that there is very little I can find on how to access RRAS and NAT on the WInXP box. Thanks John ------------------------------------------------------------------- Dr John P. Fletcher Tel: (44) 121 359 3611 ext 4625 Chemical Engineering and Applied Chemistry (CEAC), School of Engineering and Applied Science (SEAS), Aston University, Fax: (44) 121 359 4094 Aston Triangle, Email: J.P...@as... BIRMINGHAM B4 7ET U.K. CEAC Web site http://www.ceac.aston.ac.uk/ |
Thanks for helping keep SourceForge clean.
X