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

[<2...@pe...>]

On Wed, 23 Jan 2008, Henry Nestler wrote:

>>> Try other port for remapping, for example
>>>   tcp:2222:22/tcp:4000:80
>>> Than on the windows side the port 4000 is your webserver and port 80
>>> inside coLinux. Type the URL http://localhost:4000/ in your Windows browser.
>> 
>> Remapping, both work.Now I really don't have any idea why using the
>> same ports doesn't.
>
> Only one program can agent as server on one tcp port.
> If you have a running program that is listen on port 80 (windows web
> Server ?), than an other program can not open the same port for listen.
> Or ir can open, but windows is faster and catch all the incommings. I
> don't know.
>
> Has your windows some more protections to not open ports lower than 1024
> from a user program as server? Some firewalls or secure tools forbidden
> and and blocks it (Zone Alarm, Norton, ...).
>
> For example on Linux an user land program can only listen on ports
>> 1023. On ports 22 and 80 only a user "root" can listen.

I don't know what caused it, but now everything works. I 
changed it to

eth0=slirp,,tcp:2222:22/tcp:80:80/tcp:8080:8080

and it works if I use in 80 or 8080.

But if I recall correctly, when it didn't work, dhcpcd had set 
my IP to 10.0.2.16. Now it's 10.0.2.15. Does it change anything 
it the IP isn't 10.0.2.15 ? Sometimes dhcpcd doesn't offer 
10.0.2.15.

When it didn't work, I could connect from coLinux to localhost 
and 10.0.2.16.

Anyway, thanks for your help.