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
> 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
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"
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)
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
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 r
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 sta
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 route
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, g
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'
@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 t
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:
s
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 h
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
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
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
an
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:
s
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 d
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: c
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 aou
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
>>
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 1
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
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: co
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.
25 matches
Mail list logo
