[coLinux-users] Slirp port mapping problem

[<r.b...@co...>]

Hi,

I'm using coLinux 0.7.1pre with only Slirp as network in the configuratio=
n:

	eth0=3Dslirp,,tcp:10022:22/tcp:15901:5901

Linux is Gentoo, the 2005.1 image from Sourceforge, working fine includin=
g all
network operations to the outside.

My problem is that I cannot connect from Windows, I've tried ssh and vncv=
iewer.

Details:

- colinux-slirp-net-daemon is working fine, I can see it listening to bot=
h ports
and spawning (or forking) a process when I try to connect.

- sshd in Linux is working fine, it is listening, and I can connect from =
Linux
to 127.0.0.1 and also to 192.168.0.40 which are the local addresses of th=
e network.

- I can connect to anything (tested http, ssh, rsync) from Linux to outsi=
de
(outside being Windows (192.168.10.2 both netmasks are /24), or the Inter=
net).

- I cannot connect from outside to Linux (tested from Windows and from an=
other
computer via mapping the port at the gateway).  The initial connection is=
 made,
for instance ssh -> colinux-slirp-net-daemon port 10022, a process is spa=
wned on
a new port and ssh changes to that port, then nothing... until ssh closes=
 the
connection and the slirp daemon answers to that close (I used snoop under=

Solaris to see the traffic).  The result with VNC is similar, just the po=
rts change.

- there is no firewall at Windows' side, and none I could find at Gentoo =
Linux
side.  I installed syslog-ng in Linux and there are no messages about the=
 failed
connection, sshd never sees the try.

Did I miss something in the configuration?

Is anybody using the Gentoo image with slirp port mapping? One solution I=
'm
willing to try is installing Gentoo 2006.1 to another root filesystem.

Any ideas/help will be appreciated.
--=20
Ren=E9 Berber