Re: [coLinux-users] Slirp port mapping problem

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

Ren=E9 Berber wrote:
> Hi,
>=20
> I'm using coLinux 0.7.1pre with only Slirp as network in the configurat=
ion:
>=20
> 	eth0=3Dslirp,,tcp:10022:22/tcp:15901:5901
>=20
> Linux is Gentoo, the 2005.1 image from Sourceforge, working fine includ=
ing all
> network operations to the outside.
>=20
> My problem is that I cannot connect from Windows, I've tried ssh and vn=
cviewer.
>=20
> Details:
>=20
> - colinux-slirp-net-daemon is working fine, I can see it listening to b=
oth ports
> and spawning (or forking) a process when I try to connect.
>=20
> - sshd in Linux is working fine, it is listening, and I can connect fro=
m Linux
> to 127.0.0.1 and also to 192.168.0.40 which are the local addresses of =
the network.
>=20
> - I can connect to anything (tested http, ssh, rsync) from Linux to out=
side
> (outside being Windows (192.168.10.2 both netmasks are /24), or the Int=
ernet).
>=20
> - I cannot connect from outside to Linux (tested from Windows and from =
another
> 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 s=
pawned on
> a new port and ssh changes to that port, then nothing... until ssh clos=
es the
> connection and the slirp daemon answers to that close (I used snoop und=
er
> Solaris to see the traffic).  The result with VNC is similar, just the =
ports change.
>=20
> - there is no firewall at Windows' side, and none I could find at Gento=
o Linux
> side.  I installed syslog-ng in Linux and there are no messages about t=
he failed
> connection, sshd never sees the try.
>=20
> Did I miss something in the configuration?
>=20
> 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.
>=20
> Any ideas/help will be appreciated.

You know that, inside coLinux sshd is listen on 10.0.2.15 network!=20
Check it with "netstat -an".  Sshd should listen on all networks=20
(0.0.0.0:22) or on your slirp network (10.0.2.15:22).  Slirp only works=20
with ipaddress 10.0.2.15, with only the netmask 255.255.255.0, check it.=20
  Check the broadcast 10.0.2.255

Try "ssh 10.0.2.15" inside coLinux.

SSHD locks in the DNS or /etc/hosts for the windows side address=20
10.0.2.2, this was a very long timeout for me.  I wrote this lines into=20
my /etc/hosts, and than sshd runs very fine (SuSE 9.0):
   10.0.2.2        slirp-router
   10.0.2.3        slirp-dns
   10.0.2.15       slirp-client

10.0.2.2 is your default route. Right?  Check the /etc/resolv.conf

Terminate the sshd daemon and run it in foreground with verbose messages=20
"sshd -D -d"

192.168.0.* I'm afraid, is your TAP driver rigth?  If you have tap and=20
slirp configured: Shutting down the tap by "ifconfig ethX" and try only=20
the slirp.  After slirp is running, enable tap again.  Tap is typical a=20
network only betwen windows and linux (not outgoing).

Have you a file /etc/host.allow|deny?  Is there configured right? (I'm=20
not shure with this for sshd)

On windows side:
Check, that your ethernet card (192.168.10.2 I think) is listen on port=20
10022 "netstat.exe -an", or 0.0.0.0 for all networks.
Try SSH connection with putty from Windows to "localhost" port 10022.

--=20
Henry Nestler