|
Home > Archive > Linux Debian support > January 2007 > Routing problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Hans Poppe 2007-01-06, 7:18 pm |
| Hi, I've installed an Etch and it has IP 192.168.1.216/24. I'm trying to
ping 192.168.1.215/24 an all I get is "no route to host". How can this be?
It's on the same subnet.
The route command shows nothing out of the ordinary.
Any ideas?
Hans Poppe
Oslo, Norway
--
"As we enjoy great advantages from the inventions of others, we should be
glad of an opportunity to serve others with any invention of ours, and this
we should do freely and generously."
-- Benjamin Franklin
| |
| Peter J Ross 2007-01-06, 7:18 pm |
| On Sat, 30 Dec 2006 14:03:48 +0100, Hans Poppe <hpoppe@online.no>
wrote in alt.os.linux.debian:
> Hi, I've installed an Etch and it has IP 192.168.1.216/24. I'm trying to
> ping 192.168.1.215/24 an all I get is "no route to host". How can this be?
> It's on the same subnet.
> The route command shows nothing out of the ordinary.
> Any ideas?
You shouldn't be using a netmask, i.e. /24, when using ping.
$ ping 192.168.1.215
If that doesn't work, I suspect that there's a firewall in the way.
If you're unsure about the uses of IP numbers and netmasks, I
recommend the Networking Concepts HOWTO:
<http://www.netfilter.org/documentat...epts-HOWTO.html>
See expecially chapter 4.
> Hans Poppe
> Oslo, Norway
By the way, thank you for our Christmas tree:
<http://news.bbc.co.uk/1/hi/england/london/6216746.stm>
Godt Nytt År!
PJR :-)
--
xmas: A Mistletoe Avoidance System for X.
| |
| Hans Poppe 2007-01-06, 7:18 pm |
| Peter J Ross wisely stated:
> On Sat, 30 Dec 2006 14:03:48 +0100, Hans Poppe <hpoppe@online.no>
> wrote in alt.os.linux.debian:
>
>
> You shouldn't be using a netmask, i.e. /24, when using ping.
>
> $ ping 192.168.1.215
>
> If that doesn't work, I suspect that there's a firewall in the way.
>
> If you're unsure about the uses of IP numbers and netmasks, I
> recommend the Networking Concepts HOWTO:
>
>
<http://www.netfilter.org/documentat...epts-HOWTO.html>
>
> See expecially chapter 4.
>
>
> By the way, thank you for our Christmas tree:
> <http://news.bbc.co.uk/1/hi/england/london/6216746.stm>
>
> Godt Nytt År!
>
> PJR :-)
I'm not using /24 to ping ;-)
The two machines are on the same LAN, no firewall between them.
Both machines have only one NIC, one running Etch the other running Kubuntu
6.06.
The machine I'm trying to reach is reachable from other machines in the LAN,
both Linux and Windows. (There are 62 workstations and a few servers in the
LAN). Had this been a firewall problem I think I should have gotten
something like "connection refused" when pinging or trying ssh, not
this "no route to host", especially since I' using IP address, no DNS or
such.
Regarding the X-mas tree; you are most welcome!
Happy neew year!
Hans Poppe
Oslo, Norway
--
"As we enjoy great advantages from the inventions of others, we should be
glad of an opportunity to serve others with any invention of ours, and this
we should do freely and generously."
-- Benjamin Franklin
| |
| Moe Trin 2007-01-06, 7:18 pm |
| On Sun, 31 Dec 2006, in the Usenet newsgroup alt.os.linux.debian, in article
<zvSdne-fWvh4HQrYRVnzvQ@telenor.com>, Hans Poppe wrote:
>Peter J Ross wisely stated:
[vbcol=seagreen]
[vbcol=seagreen]
[vbcol=seagreen]
>The two machines are on the same LAN, no firewall between them.
/sbin/iptables -L _on_ the systems.
>The machine I'm trying to reach is reachable from other machines in the LAN,
>both Linux and Windows. (There are 62 workstations and a few servers in the
>LAN). Had this been a firewall problem I think I should have gotten
>something like "connection refused" when pinging or trying ssh,
Not for ping. Yes, you would see that for ssh.
>not this "no route to host",
"no route to host" means that "this" host knows how to reach the "other"
system (not a routing or hostname resolution problem), but local packet
delivery is made using MAC addresses. When "this" computer tried to
find the MAC address of the "other" system ("192.168.1.215, where are
you???") is received no answer to the ARP request. Look at the output of
'/sbin/arp -a' and you'll see
? (192.168.1.215) at <incomplete> on eth0
which means (?) I don't know the name (not a problem), and (<incomplete> )
I can't hear the other system that is supposedly on this network.
Do you have a cable problem? Or is the NIC otherwise mis-configured?
Old guy
|
|
|
|
|