Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[Henry N. <Hen...@Ar...>]

Josep Ma [JAZ] wrote:
> As you say, you have to use a syntax like 
> "eth0=slirp,,tcp:22:22/tcp:80:80" to open ports from colinux in slirp mode.
> 
> Let's verify a few steps:
> 
> How have you configured the eth in linux?
> you know you have to use the IP 10.0.2.15/24 , the gateway 10.0.2.2, and 
> the DNS server 10.0.2.3, do you? (Configuring it with DHCP should also 
> work).

Be shure to have netmask 255.255.255.0
All other, or default generated netmask for ip 10.0.2.15 dos't work.

> Do you get to internet from colinux?
> Ping doesn't work with slirp, but you can try telnet, ssh, wget....
> 
> Now, if that works, how do you try to connect to colinux from windows? 
> Slirp connection makes colinux act as if it was the windows machine. 
> This means that you have to connect to localhost. Example: 
> http://localhost/ should connect to an http server in colinux, if using 
> the above eth0 configuration. (That is, of course, if there port isn't 
> already used in windows).
> 
> If that still doesn't work, you would need to be more specific as to 
> which configuration are you using and how do you try to use it.

Yes. Plesase check the steps from one to other network step by step.
First inside coLinux check the running webserver, for example
$ cd /tmp
$ wget http://localhost/
Would get your index.htm without errors.
$ wget http://10.0.2.15/
Should do the same without error.

Go to windows side and open your browser with url
http://localhost/
Should get your index.htm on windows.
If not, check your firewall. Disable firewall temporaly, shutdown and
start colinux again.

If that not helps, check the running processes inside taskman.
colinux-slirp-net-daemon.exe must run and should have the parameters
"tcp:22:22/tcp:80:80". If taskman dos't give you the parameters, use the
ProcessExplorer from http://www.sysinternals.com (redirection to MS).

After the process parameter are ok, than check the listen port on tcp.
You can do it also with ProcessExplorer or with tcpView.exe (from
http://www.sysinternals.com). YOu should see an listen 0.0.0.0 on port
22 and 80.

-- 
Henry N.