Re: ssh: no route to host
On Mon, 25 Jul 2011 00:29:52 +0200, François TOURDE wrote:
> Le 15179ième jour après Epoch,
> Camaleón écrivait:
>
>> On Sat, 23 Jul 2011 23:22:57 +0200, François TOURDE wrote:
> [...]
>>>
>>> No route to host means: "I or some other router on the road can't find
>>> the hardware associated with the IP given, or the way to reach it".
>>
>> (...)
>>
>> "No route to host" is a generic message that you can get on very
>> different situations.
>
> "No route to host" is the consequence of receiving an ICMP "host
> unreachable" error. It means the ARP resolution failed for reaching the
> next hop.
A host can be "unreachable" due to many causes.
(...)
> When your ISP, like mine, is blocking the xx port, you should receive a
> "connection timed out" message.
>
> That's what I receive:
>
> francois@fermat:~$ telnet gmail.com 25 Trying 209.85.147.17...
> telnet: Unable to connect to remote host: Connection timed out
That response ("connection timed out") looks like a kind of filter in
between.
> But perhaps you didn't receive the same error?
Not in my case. I simply got "No route to host" message.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.25.14.55...@gmail.com
Re: ssh: no route to host
> François TOURDE writes: > Le 15179ième jour après Epoch, Camaleón écrivait: > On Sat, 23 Jul 2011 23:22:57 +0200, François TOURDE wrote: >>> No route to host means: "I or some other router on the road can't find >>> the hardware associated with the IP given, or the way to reach it". >> "No route to host" is a generic message that you can get on very >> different situations. > "No route to host" is the consequence of receiving an ICMP "host > unreachable" error. It means the ARP resolution failed for reaching > the next hop. … Or ICMP “host unreachable — admin prohibited filter”? See, e. g., [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=490854 >> For instance, when your ISP has smtp port of your DSL connection closed >> and you try to establish a connection on port 25 via telnet with a remote >> e-mail server, you get a "no route to host" message which basically means >> that you cannot establish a connection with the selected computer on >> choosen port but it does not invlove that computer you are trying to >> reach is "off" or disconnected. > When your ISP, like mine, is blocking the xx port, you should receive > a "connection timed out" message. > That's what I receive: > francois@fermat:~$ telnet gmail.com 25 > Trying 209.85.147.17... > telnet: Unable to connect to remote host: Connection timed out > But perhaps you didn't receive the same error? That's what happens when the packets are dropped, without any ICMP message whatsoever. In iptables(8) terms, compare: -A FORWARD -d 192.0.2.0/24 -p tcp -m tcp --dport 25 -j DROP -A FORWARD -d 192.0.2.0/24 -p tcp -m tcp --dport 25 -j REJECT --reject-with icmp-admin-prohibited -- FSF associate member #7257 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/86sjpvt7ev@gray.siamics.net
Re: ssh: no route to host
Le 15179ième jour après Epoch, Camaleón écrivait: > On Sat, 23 Jul 2011 23:22:57 +0200, François TOURDE wrote: [...] >> >> No route to host means: "I or some other router on the road can't find >> the hardware associated with the IP given, or the way to reach it". > > (...) > > "No route to host" is a generic message that you can get on very > different situations. "No route to host" is the consequence of receiving an ICMP "host unreachable" error. It means the ARP resolution failed for reaching the next hop. > For instance, when your ISP has smtp port of your DSL connection closed > and you try to establish a connection on port 25 via telnet with a remote > e-mail server, you get a "no route to host" message which basically means > that you cannot establish a connection with the selected computer on > choosen port but it does not invlove that computer you are trying to > reach is "off" or disconnected. When your ISP, like mine, is blocking the xx port, you should receive a "connection timed out" message. That's what I receive: francois@fermat:~$ telnet gmail.com 25 Trying 209.85.147.17... telnet: Unable to connect to remote host: Connection timed out But perhaps you didn't receive the same error? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei1ftiqn@fermat.tourde.home
Re: ssh: no route to host
On Sat, 23 Jul 2011 23:22:57 +0200, François TOURDE wrote: > Le 15177ième jour après Epoch, > Camaleón écrivait: > >> "No route to host" usually means "I cannot see the machine at all" and >> "I cannot see the machine at all" usually involves: >> >> a) SSH service is not running on the client b) IP of the client is >> unreachable > > I don't agree with that. > > No route to host means: "I or some other router on the road can't find > the hardware associated with the IP given, or the way to reach it". (...) "No route to host" is a generic message that you can get on very different situations. For instance, when your ISP has smtp port of your DSL connection closed and you try to establish a connection on port 25 via telnet with a remote e-mail server, you get a "no route to host" message which basically means that you cannot establish a connection with the selected computer on choosen port but it does not invlove that computer you are trying to reach is "off" or disconnected. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.07.24.13.58...@gmail.com
Re: ssh: no route to host
Le 15177ième jour après Epoch, Camaleón écrivait: > "No route to host" usually means "I cannot see the machine at all" and "I > cannot see the machine at all" usually involves: > > a) SSH service is not running on the client > b) IP of the client is unreachable I don't agree with that. No route to host means: "I or some other router on the road can't find the hardware associated with the IP given, or the way to reach it". The reasons are often: 1) machine is power off/unplugged/whatever that involves ARP resolution. 2) the routes (default or other) are pointing to a wrong interface. Please, OP, could you post the result of the "route" or "ip route" command on the originating machine and the router? And what kind of router is it? Try also to send a ping from the destination machine to the ssh-originating one, and then ssh it again, to see if it changes something. Anyway, sending us the results of "ifconfig" on each peer is also a good idea. HTH. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mxg4u1xq@fermat.tourde.home
Re: ssh: no route to host
On Wed, 20 Jul 2011 14:51:45 -0500, Hugo Vanwoerkom wrote:
> Camaleón wrote:
>> On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote:
>>
>> (...)
>>
>>> Every so often when I connect from the desktop to the laptop with ssh,
>>> I get:
>>>
>>> ssh: connect to host 192.168.1.194 port 22: No route to host
>>
>> (...)
>>
>> Yep, as Walter suggested, this can be a problem with DHCP that has
>> given another IP to the laptop. If you have only two machines in the
>> LAN, give them static IPs so you don't have to depend on your router's
>> DHCP eccentricities :-)
>>
>>
> But the IP should show up in ifconfig, no?
Yes, please run it ("/sbin/ifconfig") and put here the output.
> And that did not change after the failure...
We cannot know unless you provide additional data :-)
"No route to host" usually means "I cannot see the machine at all" and "I
cannot see the machine at all" usually involves:
a) SSH service is not running on the client
b) IP of the client is unreachable
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.07.22.16.00...@gmail.com
Re: ssh: no route to host
Joe wrote: On Thu, 21 Jul 2011 19:55:16 +0100 Brian wrote: On Wed 20 Jul 2011 at 14:51:45 -0500, Hugo Vanwoerkom wrote: Camaleón wrote: Yep, as Walter suggested, this can be a problem with DHCP that has given another IP to the laptop. If you have only two machines in the LAN, give them static IPs so you don't have to depend on your router's DHCP eccentricities :-) But the IP should show up in ifconfig, no? And that did not change after the failure... The advice is still not unsound though. It will take DHCP out of consideration. Is the problem one which appears after being able to ssh to the laptop successfully at some earlier time, like 5 minutes ago? What happens with ping/traceroute/ssh/telnet/route/arp from desktop to laptop and vice versa? Is there wireless on either machine? Does taking down the firewall on the router make any difference? Another line of thought: being a laptop, does it go into standby or hibernation? Debian doesn't have a great record for waking up the machine properly afterwards. Not without first doing some research using Ubuntu... No, as I said, the problem only occurs after doing a reboot on the laptop Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j0c2sc$ap0$1...@dough.gmane.org
Re: ssh: no route to host
Brian wrote: On Wed 20 Jul 2011 at 14:51:45 -0500, Hugo Vanwoerkom wrote: Camaleón wrote: Yep, as Walter suggested, this can be a problem with DHCP that has given another IP to the laptop. If you have only two machines in the LAN, give them static IPs so you don't have to depend on your router's DHCP eccentricities :-) But the IP should show up in ifconfig, no? And that did not change after the failure... The advice is still not unsound though. It will take DHCP out of consideration. Is the problem one which appears after being able to ssh to the laptop successfully at some earlier time, like 5 minutes ago? What happens with ping/traceroute/ssh/telnet/route/arp from desktop to laptop and vice versa? Is there wireless on either machine? Does taking down the firewall on the router make any difference? No, the "problem" occurs only after I reboot the laptop. After rebooting, sometimes, the no route message appears after trying to ssh from the desktop. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j0c1u1$40l$1...@dough.gmane.org
Re: ssh: no route to host
On Thu, 21 Jul 2011 19:55:16 +0100 Brian wrote: > On Wed 20 Jul 2011 at 14:51:45 -0500, Hugo Vanwoerkom wrote: > > > Camaleón wrote: > >> > >> Yep, as Walter suggested, this can be a problem with DHCP that has > >> given another IP to the laptop. If you have only two machines in > >> the LAN, give them static IPs so you don't have to depend on your > >> router's DHCP eccentricities :-) > >> > > > > But the IP should show up in ifconfig, no? And that did not change > > after the failure... > > The advice is still not unsound though. It will take DHCP out of > consideration. > > Is the problem one which appears after being able to ssh to the laptop > successfully at some earlier time, like 5 minutes ago? What happens > with ping/traceroute/ssh/telnet/route/arp from desktop to laptop and > vice versa? Is there wireless on either machine? Does taking down the > firewall on the router make any difference? > > Another line of thought: being a laptop, does it go into standby or hibernation? Debian doesn't have a great record for waking up the machine properly afterwards. Not without first doing some research using Ubuntu... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110722082917.72be9...@jresid.jretrading.com
Re: ssh: no route to host
On Wed 20 Jul 2011 at 14:51:45 -0500, Hugo Vanwoerkom wrote: > Camaleón wrote: >> >> Yep, as Walter suggested, this can be a problem with DHCP that has >> given another IP to the laptop. If you have only two machines in the >> LAN, give them static IPs so you don't have to depend on your router's >> DHCP eccentricities :-) >> > > But the IP should show up in ifconfig, no? And that did not change after > the failure... The advice is still not unsound though. It will take DHCP out of consideration. Is the problem one which appears after being able to ssh to the laptop successfully at some earlier time, like 5 minutes ago? What happens with ping/traceroute/ssh/telnet/route/arp from desktop to laptop and vice versa? Is there wireless on either machine? Does taking down the firewall on the router make any difference? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110721185516.GF29162@desktop
Re: ssh: no route to host
@Hugo: It might be related to your /etc/hosts.allow /etc/hosts.deny configuration. With DHCP your internal subnet should not change. You can use this to set up an access rule for sshd - please refer to the debian administrators guide [1] on securing ssh access for the details. I'll only give the most likely setup for your laptop: In /etc/hosts.allow you set up an access allow rule for your local subnet (192.168.1.xxx) - please not this rule will only affect the ssh daemon: # /etc/hosts.allow sshd: 192.168.1.0/24 sshd: localhost In /etc/hosts.deny I recommend you deny any other sshd access for maximum security: # /etc/hosts.deny sshd: ALL That should be it - now it shouldn't matter anymore what ip address you dhcp server has offered you, as long as it puts you into the same subnet. [1] http://www.debian-administration.org/articles/87 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp4e24951a7dc2d8c6e47c2d8...@phx.gbl
Re: ssh: no route to host
Walter Hurry wrote: On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: Hi, my home network consist of a desktop and a laptop connected to a router that goes to the internet. The firewall is on the router. Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host The way I get aound that is to power off the laptop and reboot it That seems a dumb way to do it. How is that resolved without rebooting? Are you using DHCP? Next time it happens, go to the laptop and look at what ifconfig has to say before you reboot it. Looked at ifconfig and it looked the same as when I can ssh. Still he only way I can "fix" this is by powering off/on. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j07bi0$3a0$1...@dough.gmane.org
Re: ssh: no route to host
Camaleón wrote: On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: (...) Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host (...) Yep, as Walter suggested, this can be a problem with DHCP that has given another IP to the laptop. If you have only two machines in the LAN, give them static IPs so you don't have to depend on your router's DHCP eccentricities :-) But the IP should show up in ifconfig, no? And that did not change after the failure... Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j07bkh$2g9$2...@dough.gmane.org
Re: ssh: no route to host
Greg Madden wrote: On Wednesday 20 July 2011 07:17:29 am Walter Hurry wrote: On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: Hi, my home network consist of a desktop and a laptop connected to a router that goes to the internet. The firewall is on the router. Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host The way I get aound that is to power off the laptop and reboot it That seems a dumb way to do it. How is that resolved without rebooting? Are you using DHCP? Next time it happens, go to the laptop and look at what ifconfig has to say before you reboot it. Before a reboot try from a term as root: 1. 'dhclient ethX' : 2. 'service networking restart' I did that and it did not resolve he problem. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j07be2$2g9$1...@dough.gmane.org
Re: ssh: no route to host
On Wednesday 20 July 2011 07:17:29 am Walter Hurry wrote: > On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: > > Hi, > > > > my home network consist of a desktop and a laptop connected to a router > > that goes to the internet. The firewall is on the router. > > > > Every so often when I connect from the desktop to the laptop with ssh, I > > get: > > > > ssh: connect to host 192.168.1.194 port 22: No route to host > > > > The way I get aound that is to power off the laptop and reboot it > > > > That seems a dumb way to do it. > > > > How is that resolved without rebooting? > > Are you using DHCP? Next time it happens, go to the laptop and look at > what ifconfig has to say before you reboot it. Before a reboot try from a term as root: 1. 'dhclient ethX' : 2. 'service networking restart' -- Peace, Greg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107201013.28225.gomadtr...@gci.net
Re: ssh: no route to host
On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: (...) > Every so often when I connect from the desktop to the laptop with ssh, I > get: > > ssh: connect to host 192.168.1.194 port 22: No route to host (...) Yep, as Walter suggested, this can be a problem with DHCP that has given another IP to the laptop. If you have only two machines in the LAN, give them static IPs so you don't have to depend on your router's DHCP eccentricities :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.07.20.15.28...@gmail.com
Re: ssh: no route to host
Walter Hurry wrote: On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: Hi, my home network consist of a desktop and a laptop connected to a router that goes to the internet. The firewall is on the router. Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host The way I get aound that is to power off the laptop and reboot it That seems a dumb way to do it. How is that resolved without rebooting? Are you using DHCP? Next time it happens, go to the laptop and look at what ifconfig has to say before you reboot it. Yes, using DHCP -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j06rqj$hbr$3...@dough.gmane.org
Re: ssh: no route to host
On Wed, 20 Jul 2011 11:17:29 -0400, Walter Hurry wrote: On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: Hi, my home network consist of a desktop and a laptop connected to a router that goes to the internet. The firewall is on the router. Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host The way I get aound that is to power off the laptop and reboot it That seems a dumb way to do it. How is that resolved without rebooting? Are you using DHCP? Next time it happens, go to the laptop and look at what ifconfig has to say before you reboot it. Also see if you can ping the laptop to eliminate the possibility of the error being the laptop dropping its connection. -- Michael Checca echo "complaints" > /dev/null -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/op.vyxbnkmo4b8ft1@michael-laptop
Re: ssh: no route to host
On Wed, 20 Jul 2011 10:05:24 -0500, Hugo Vanwoerkom wrote: > Hi, > > my home network consist of a desktop and a laptop connected to a router > that goes to the internet. The firewall is on the router. > > Every so often when I connect from the desktop to the laptop with ssh, I > get: > > ssh: connect to host 192.168.1.194 port 22: No route to host > > The way I get aound that is to power off the laptop and reboot it > > That seems a dumb way to do it. > > How is that resolved without rebooting? Are you using DHCP? Next time it happens, go to the laptop and look at what ifconfig has to say before you reboot it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j06ri9$fs4$2...@dough.gmane.org
ssh: no route to host
Hi, my home network consist of a desktop and a laptop connected to a router that goes to the internet. The firewall is on the router. Every so often when I connect from the desktop to the laptop with ssh, I get: ssh: connect to host 192.168.1.194 port 22: No route to host The way I get aound that is to power off the laptop and reboot it That seems a dumb way to do it. How is that resolved without rebooting? Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j06qr4$hbr$1...@dough.gmane.org
Re: ssh: No route to host
Guillaume TESSIER wrote: > John Wilkes wrote: > >> On Fri, 2005-06-17 at 22:56 +0200, Guillaume TESSIER wrote: >> >> >>> 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! >>> >> >> >> >> True! I've got a fairly good idea of what it is now though, thanks. >> >> >> >>> 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. >>> >> >> >> >> I guess that's the next angle of attack. It's strange that it worked >> before but it doesn't work now, when the only thing I've changed is the >> OS on the computer. I'll have a look at the admin page on the router. >> >> >> >>> But it's clear that you can't ping a machine from you lan from the >>> internet. >>> >>> G >>> >>> >> >> >> >> >> >> > You're welcome > > Hey, i just thought about something : > > after reinstalling your mother's machine, maybe you didn't assign it > the same IP. > Your router has maybe the right NAT tables (it could explain why it > worked before), but it can't find the machine on your LAN because you > changed its IP. > > That's a possibility. But you should definitely check your router > settings. > > G > > Is the IP address the router receives from the ISP dynamic. If yes, it could have changed (rfc from someone more knowledgeble about dhcp wrt changing dhcp clients). You could be pinging a machine which is now occupying the IP address your mother formerly had -- one which doesn't run ssh. -- Geoffrey D. Jacobs MORE CORE AVAILABLE, BUT NONE FOR YOU. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh: No route to host
John Wilkes wrote: On Fri, 2005-06-17 at 22:56 +0200, Guillaume TESSIER wrote: 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! True! I've got a fairly good idea of what it is now though, thanks. 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. I guess that's the next angle of attack. It's strange that it worked before but it doesn't work now, when the only thing I've changed is the OS on the computer. I'll have a look at the admin page on the router. But it's clear that you can't ping a machine from you lan from the internet. G You're welcome Hey, i just thought about something : after reinstalling your mother's machine, maybe you didn't assign it the same IP. Your router has maybe the right NAT tables (it could explain why it worked before), but it can't find the machine on your LAN because you changed its IP. That's a possibility. But you should definitely check your router settings. G -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh: No route to host
John Wilkes wrote: Hello List, I've recently transferred my computer and my mother's over to Debian. They were both running SuSE before. I used to ssh to my mother's computer to perform maintenance, but that doesn't work now. When I try to ssh to her computer, I get the error message: ssh: connect to host XXX.XXX.XXX.XXX port 22: No route to host My mother's computer is hiding behind a router which acts as a firewall, but port 22 is open - it worked with SuSE and I haven't changed the settings. There is no software firewall, at least none that I'm aware of. My computer has Lokkit installed; I've told this to expect ssh, but no joy. I've also switched it off altogether with no change. (this is only for incoming ssh, though...?) I can ping my mother's computer, so it's not the network that's at fault. The sshd_config file is the one installed by default. Both computers are running Sarge with a 2.6.8 kernel. I'd be very grateful for any ideas on this. What do you mean by saying you can ping your mother's computer ? Maybe, your pb comes from the NAT config of your router G -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ssh: No route to host
Hello List, I've recently transferred my computer and my mother's over to Debian. They were both running SuSE before. I used to ssh to my mother's computer to perform maintenance, but that doesn't work now. When I try to ssh to her computer, I get the error message: ssh: connect to host XXX.XXX.XXX.XXX port 22: No route to host My mother's computer is hiding behind a router which acts as a firewall, but port 22 is open - it worked with SuSE and I haven't changed the settings. There is no software firewall, at least none that I'm aware of. My computer has Lokkit installed; I've told this to expect ssh, but no joy. I've also switched it off altogether with no change. (this is only for incoming ssh, though...?) I can ping my mother's computer, so it's not the network that's at fault. The sshd_config file is the one installed by default. Both computers are running Sarge with a 2.6.8 kernel. I'd be very grateful for any ideas on this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
