Menu
▾
▴
Re: [coLinux-devel] Win2k ICS 192.168.0.1 Conflict
|
From: Nathan C. <nat...@ya...> - 2004-04-24 06:38:00
|
Hello Jamie, Here is my solution to the problem. I frequently use a nearby unsecured access point (not owned or managed by me). The IP address given to me is from 192.168.0.1, thus I cannot used Windows' ICS. This to me is a foolish limitation of ICS (the fact that you cannot configure the subnet used by ICS). So this is what I do. I turn off ICS. I set the IP address of the TAP adapter to 10.0.0.1 and set the CoLinux installation to be on the same subnet. I then run an HTTP proxy server on Windows and set CoLinux to use the proxy. The proxy server I use is: http://sourceforge.net/projects/scache/ This takes a little extra work, and isn't a direct connection, but I can do most anything I need to do through the proxy and it really doesn't take much time to make the configuration changes. Actually, I wish changing the network configuration on Windows was as quick and easy as it is in Linux... I hope this helps. --Nathan Jamie Alessio <ja...@ja...> wrote: I installed coLinux about a week ago and have it up and running smoothly on my IBM Thinkpad laptop running Win2k. The laptop has both a built-in ethernet card and a wireless pcmcia card. I had no problems using the bridged networking setup to get the coLinux instance full network access over built-in ethernet, but I would really like to get it working over my wireless link since that's what I typically use on the laptop. According to the coLinux wiki WinPCAP does not work for wireless connections so the bridged setup is out. But, it seems that I should be able to use the TAP-Win32 plus Internet Connection Sharing setup to get the wireless card to route traffic from coLinux. At the moment I'm hitting a very Windows-ish wall that I can't get past - when I enable Internet Connection Sharing on the wireless card Windows forces the IP address to be 192.168.0.1. The problem is that that IP address is already in use on the wireless access point/router I am connected to and thus Windows fails to activate Internet Connection Sharing since it can't allocate 192.168.0.1 for itself. I suppose one simple solution is to just change the IP address of the router but it is physically located in another building and I do not have admin access to it. So, how do you use the TAP-Win32 plus Internet Connection Sharing solution on Win2k on a network that already has 192.168.0.1 allocated? Surely someone else must be on a network using that IP as a gateway and or dhcp server and has run into this already? - Jamie ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel --------------------------------- Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ |