Re: [coLinux-users] Slirp port mapping problem

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

Henry Nestler wrote:
[snip]
> 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=
=2E=20

sshd is listening on 0.0.0.0:22 (by default it also listens on the ipv6 a=
ddress
but I disabled it to see if it helped).

The Linux eth0 address is not the one you mention, it is 192.168.0.40 and=
 it
receives that address from a DHCP server which I guess is the slirp-daemo=
n since
I have only one DHCP server and that one did not give that address.

I don't use that network, but I see in the comments of Gentoo's network
configuration that is seems to be the default Gentoo network.

>   Check the broadcast 10.0.2.255

Yes, broadcast is 10.0.2.255, so networking is set all wrong

> Try "ssh 10.0.2.15" inside coLinux.

ssh connected to my sshd running in Windows.

> SSHD [locks]looks 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
>=20
> 10.0.2.2 is your default route. Right?  Check the /etc/resolv.conf

Yes, 10.0.2.2 is the default route, and 'slirp-dns' is the DNS server.

> Terminate the sshd daemon and run it in foreground with verbose message=
s=20
> "sshd -D -d"
>=20
> 192.168.0.* I'm afraid, is your TAP driver rigth?

I disabled TAP, I'm not using it.

> 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).
>=20
> Have you a file /etc/host.allow|deny?  Is there configured right? (I'm =

> not shure with this for sshd)

Yes, I know very well how sshd works with those files (I'm using DenyHost=
s and
fail2ban on some servers).

> 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.

Yes, slirp-daemon is listening on the ports I configured.

> Try SSH connection with putty from Windows to "localhost" port 10022.

The result is what I reported before.

The problem, as you pointed out in your first comment, is that I have an =
IP
address that does not belong to the Linux network.  I have to find out wh=
ich
DHCP server gave that address or from where it comes from.  A quick solut=
ion is
to set a fixed IP address using 10.0.2.15 .

Thanks for your reply, it was very helpful.
--=20
Ren=E9 Berber