FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 04-03-2011, 03:23 PM
Lisi
 
Default ssh between computers on my home network

On Sunday 03 April 2011 15:59:46 shawn wilson wrote:
> On Sun, Apr 3, 2011 at 2:49 PM, Lisi <lisi.reisz@gmail.com> wrote:
> > On Sunday 03 April 2011 15:33:16 shawn wilson wrote:
> >> ok, now lets see a route -n from the computers.
[snip]
> hummmmm, lets try an 'ip addr', the main thing i want to see is UP as in
> this: 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
> ... but, there's some tables info that might show an issue too.

Thanks for your patience!

It is probably relevant to the results that Junior is running a fairly minimal
installation of Etch at the moment. (It is supposed to dual boot with
Squeeze, but something has hosed the boot to it from Grub.) The other 2 are
running Lenny. I only have these 3 connected at the moment, but I could
connect another computer up if a 3rd result is needed.

Tux:/home/lisi# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:50:8d:5b:93:b1 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:90:27:75:c8:4e brd ff:ff:ff:ff:ff:ff
inet 192.168.0.2/24 brd 192.168.0.255 scope global eth1
inet6 fe80::290:27ff:fe75:c84e/64 scope link
valid_lft forever preferred_lft forever
Tux:/home/lisi#

Junior:/home/lisi# ip addr
bash: ip: command not found
Junior:/home/lisi#

Dozy:/home/peter# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
link/ether 00:0d:87:a0:44:dd brd ff:ff:ff:ff:ff:ff
inet 192.168.0.33/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20d:87ff:fea0:44dd/64 scope link
valid_lft forever preferred_lft forever
Dozy:/home/peter#

Thanks, again,
Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201104031623.03698.lisi.reisz@gmail.com">http://lists.debian.org/201104031623.03698.lisi.reisz@gmail.com
 
Old 04-03-2011, 03:35 PM
Lisi
 
Default ssh between computers on my home network

On Sunday 03 April 2011 16:15:05 Camaleón wrote:
> On Sun, 03 Apr 2011 15:18:06 +0100, Lisi wrote:
[snip]
> > lisi@Tux:~$ ping 192.168.0.3
> > PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data. From 192.168.0.2
> > icmp_seq=1 Destination Host Unreachable
>
> (...)
>
> Ugh.

Thanks, Camaleón. I had tried taht - but could not see that that was the
problem. :-(

> Is the "ping" success if you run it as root?

No! Herewith 1 specimen:

Tux:/home/lisi# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
From 192.168.0.2 icmp_seq=2 Destination Host Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.0.3 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5003ms
, pipe 3
Tux:/home/lisi#

> Also, list your "iptables -L" for all of the involved computers.

Tux:/home/lisi# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Tux:/home/lisi#


Junior:/home/lisi# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Junior:/home/lisi#


Dozy:/home/peter# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Dozy:/home/peter#

Thanks again,
Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201104031635.08507.lisi.reisz@gmail.com">http://lists.debian.org/201104031635.08507.lisi.reisz@gmail.com
 
Old 04-03-2011, 03:52 PM
Camaleón
 
Default ssh between computers on my home network

On Sun, 03 Apr 2011 16:35:08 +0100, Lisi wrote:

> On Sunday 03 April 2011 16:15:05 Camaleón wrote:

>> Is the "ping" success if you run it as root?
>
> No! Herewith 1 specimen:
>
> Tux:/home/lisi# ping 192.168.0.3

Try to ping machine .33 (ping -c 3 192.168.0.33)

And also the reverse, from "Dozy" try to ping "Tux" (ping -c 3
192.168.0.2).

>> Also, list your "iptables -L" for all of the involved computers.
>
> Tux:/home/lisi# iptables -L

Okay, there are no rules/filters in any machine so no software setting is
preventing the ping.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.04.03.15.52.14@gmail.com">http://lists.debian.org/pan.2011.04.03.15.52.14@gmail.com
 
Old 04-03-2011, 04:02 PM
shawn wilson
 
Default ssh between computers on my home network

Just curious, I don't remember you saying that you reported the 'router' device?


Also, I assume you've done some configuration changes to the router as you're using static ips? So what dhcp changes have you made? Are you sure you're not stepping on something else's feet? Does your router have logs? If so what do they say (on a layer 2 basic - I don't care about dns fwd lookups so that everyone knows your porn habits - I want to know if the interface is resting a thousand times a minute or something like that).
 
Old 04-03-2011, 04:33 PM
Lisi
 
Default ssh between computers on my home network

On Sunday 03 April 2011 16:52:14 Camaleón wrote:
> On Sun, 03 Apr 2011 16:35:08 +0100, Lisi wrote:
> > On Sunday 03 April 2011 16:15:05 Camaleón wrote:
> >> Is the "ping" success if you run it as root?
> >
> > No! Herewith 1 specimen:
> >
> > Tux:/home/lisi# ping 192.168.0.3
>
> Try to ping machine .33 (ping -c 3 192.168.0.33)

Thanks for persevering, Camaleón.

machine .33 would be the third DHCP number allocated by the router. It does
not currently exist. I could find three machines to connect by DHCP, if the
third would make a difference of some kind!
>
> And also the reverse, from "Dozy" try to ping "Tux" (ping -c 3
> 192.168.0.2).

Wow! Could you explain how you knew that? I might recognise it myself
another time!!

peter@Dozy:~$ ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=2.95 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=1.27 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.224 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=64 time=1.27 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=64 time=0.221 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=64 time=0.164 ms
64 bytes from 192.168.0.2: icmp_seq=7 ttl=64 time=1.28 ms
^C
--- 192.168.0.2 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 0.164/1.056/2.951/0.920 ms
peter@Dozy:~$

To repeat myself! Thank you. I really appreciate it.
Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201104031733.04788.lisi.reisz@gmail.com">http://lists.debian.org/201104031733.04788.lisi.reisz@gmail.com
 
Old 04-03-2011, 04:56 PM
Lisi
 
Default ssh between computers on my home network

On Sunday 03 April 2011 17:33:04 Lisi wrote:
> machine .33 would be the third *DHCP number allocated by the router. *It
> does not currently exist. *I could find three machines to connect by DHCP,
> if the third would make a difference of some kind!

I hang my head in shame! :-(

All that was needed was the installation of openssh-server and a better memory
on my part. (I had intended to change from the default Debian choice of
DHCP - and thought that I had done so.) Not mention reading the output
before I post it.

Thanks Jochem for solving the problem, Camaleón for spotting my error over IPs
and all of you, including Frank and shawn, for your remarkable patience.

I am truly contrite about the noise. :-(

An exam is involved in this - I need ot be able to access one machine from
another, and I always panic about exams. :-( Yes, it is remarkably stupid to
be panicking at my age about an exam whose result really doesn't matter in
the great scheme of things, but my irrational self still wins. :-(

I apologise profusely.

Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201104031756.23852.lisi.reisz@gmail.com">http://lists.debian.org/201104031756.23852.lisi.reisz@gmail.com
 
Old 04-03-2011, 05:20 PM
Camaleón
 
Default ssh between computers on my home network

On Sun, 03 Apr 2011 17:33:04 +0100, Lisi wrote:

> On Sunday 03 April 2011 16:52:14 Camaleón wrote:

(...)

>> And also the reverse, from "Dozy" try to ping "Tux" (ping -c 3
>> 192.168.0.2).
>
> Wow! Could you explain how you knew that? I might recognise it myself
> another time!!

I've just read that you finally put all the pieces of the puzzle in the
right order by yourself :-)

I noticed something wrong when Shawn cleverly asked you for the result of
"ip addr" command. There you can see the real IPs for the machines:

- Tux was 192.168.0.2
- Junior was out (no result from ip adrr)
- Dozy was 192.168.0.33

There was no track for "192.168.0.3" nor "192.168.0.8" (the first hosts
you wanted to reach) so the only thing we could do was trying to ping the
hosts with "known" IP addresses and hope the results of that test
provided any additional clue... which finally did.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.04.03.17.20.36@gmail.com">http://lists.debian.org/pan.2011.04.03.17.20.36@gmail.com
 
Old 04-03-2011, 05:27 PM
Lisi
 
Default ssh between computers on my home network

On Sunday 03 April 2011 18:20:37 Camaleón wrote:
> On Sun, 03 Apr 2011 17:33:04 +0100, Lisi wrote:
> > On Sunday 03 April 2011 16:52:14 Camaleón wrote:
>
> (...)
>
> >> And also the reverse, from "Dozy" try to ping "Tux" (ping -c 3
> >> 192.168.0.2).
> >
> > Wow! Could you explain how you knew that? I might recognise it myself
> > another time!!
>
> I've just read that you finally put all the pieces of the puzzle in the
> right order by yourself :-)
>
> I noticed something wrong when Shawn cleverly asked you for the result of
> "ip addr" command. There you can see the real IPs for the machines:
>
> - Tux was 192.168.0.2
> - Junior was out (no result from ip adrr)
> - Dozy was 192.168.0.33
>
> There was no track for "192.168.0.3" nor "192.168.0.8" (the first hosts
> you wanted to reach) so the only thing we could do was trying to ping the
> hosts with "known" IP addresses and hope the results of that test
> provided any additional clue... which finally did.

Thanks yet again, Camaleón! :-) A lucid explanation.

Lisi


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201104031827.33340.lisi.reisz@gmail.com">http://lists.debian.org/201104031827.33340.lisi.reisz@gmail.com
 

Thread Tools




All times are GMT. The time now is 01:35 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org