[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ssh: No route to host



John Wilkes wrote:

On Fri, 2005-06-17 at 22:21 +0200, Guillaume TESSIER wrote:
What do you mean by saying you can ping your mother's computer ?
Maybe, your pb comes from the NAT config of your router


I mean, I ping <address> and get a response. I'm not sure what you mean
by NAT config, but I assume you mean that I'm pinging the router but not
getting through to the computer. That could be the case.

How can I tell what I am actually looking at?

Thanks


NAT translation is not a concept i can resume in some lines.
But , broadly, it works like this :

For exemple, you have ssh server (your mum'smachine) that has a private (non routable through the internet) like 192.168.121.200 and listening for ssh connection onto port 22. Your routeur is the only machine that has a routable ip though the internet. And it has a NAt table (and iptables forward rules) so that when you do a ssh request on that routeur, the router pass the request to the right machine of your LAN.

Therefore, if you have several ssh serveurs in your LAN, you need them to listen onto different ports so the router can sort the requests and pass them to the right ssh server of your lan.

This is definitely not a simple task to explain it quickly!

this is a reference how to :
http://iptables-tutorial.frozentux.net/iptables-tutorial.html

However, if your routeur is a lill'box, i guess it has some web administration page that would help you a lot. But it's clear that you can't ping a machine from you lan from the internet.

G



Reply to: