Red Hat Topics - cant run ping command

Author

cant run ping command

rtripathi

2006-11-24, 1:13 pm

hi ,
i m unable to run ping command in my pc i have linux .
when i run the ping command , i recived the message

[root@yash ~]# ping 172.16.4.52
connect: No such process
[root@yash ~]#

Jean-David Beyer

2006-11-24, 7:13 pm

rtripathi wrote:
> hi ,
> i m unable to run ping command in my pc i have linux .
> when i run the ping command , i recived the message
>
> [root@yash ~]# ping 172.16.4.52
> connect: No such process
> [root@yash ~]#
>
I have no trouble running it, but it does not respond:

$ ping 172.16.4.52
PING 172.16.4.52 (172.16.4.52) 56(84) bytes of data.

--- 172.16.4.52 ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10009ms

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 20:00:01 up 34 days, 22:29, 3 users, load average: 4.66, 4.37, 4.25

noi

2006-11-25, 7:11 pm

On Sat, 25 Nov 2006 01:06:06 +0000, Jean-David Beyer wrote this:

> rtripathi wrote:
> I have no trouble running it, but it does not respond:
>
> $ ping 172.16.4.52
> PING 172.16.4.52 (172.16.4.52) 56(84) bytes of data.
>
> --- 172.16.4.52 ping statistics ---
> 11 packets transmitted, 0 received, 100% packet loss, time 10009ms
You're ping is working but your network is not or firewall prevents
ICMP traffic or an invalid ip address

$ traceroute 172.16.4.52 # to find the bottleneck

verify DNS servers and MTU size

$ ifconfig
$ route

Jan Gerrit Kootstra

2006-11-25, 7:11 pm

noi wrote:
> On Sat, 25 Nov 2006 01:06:06 +0000, Jean-David Beyer wrote this:
>
>
>
> You're ping is working but your network is not or firewall prevents
> ICMP traffic or an invalid ip address
>
> $ traceroute 172.16.4.52 # to find the bottleneck
>
> verify DNS servers and MTU size
>
> $ ifconfig
> $ route
>
>
Hi all,

A ping to 172.16.4.52 can only work if this ip-address is inside your
own network-segments.

10.abc.def.ghi
172.16.jkl.mno
192.168.pqr.stu

are ranges that are private, so cannot be used for internet ip-addresses.

If not defined at 'your' LAN they cannot be reached by ping, traceroute
or whatever.

The first issue of ping no such process if complete different issue.

Kind regards,

Jan Gerrit Kootstra

Jean-David Beyer

2006-11-25, 7:11 pm

noi wrote:
> On Sat, 25 Nov 2006 01:06:06 +0000, Jean-David Beyer wrote this:
>
[vbcol=seagreen]
> You're ping is working but your network is not or firewall prevents
> ICMP traffic or an invalid ip address
>
> $ traceroute 172.16.4.52 # to find the bottleneck

To no one's surprise, traceroute does not go far.

$ /usr/sbin/traceroute 172.16.4.52
traceroute to 172.16.4.52 (172.16.4.52), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.506 ms 0.372 ms 0.231 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *

192.168.0.1 is the (internal) IP address of my router. But RFC 1918, section
3, reserves all 172.16.*.* IP addresses to _Private Internets_. So it makes
little difference whether my firewall or my router blocks sending that out.
I imagine my ISP would block my trying to send to any addresses such as:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

>
> verify DNS servers and MTU size

DNS server is at 127.0.0.1
>
> $ ifconfig

eth2 Link encap:Ethernet HWaddr 01:02:03:04:05:06
inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:6397977 errors:0 dropped:0 overruns:0 frame:0
TX packets:3703309 errors:4 dropped:0 overruns:0 carrier:4
collisions:0 txqueuelen:1000
RX bytes:1219773553 (1163.2 Mb) TX bytes:483953893 (461.5 Mb)

> $ route

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth2
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth2

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 17:20:01 up 35 days, 19:49, 3 users, load average: 4.30, 4.11, 4.09

noi

2006-11-26, 1:12 pm

On Sat, 25 Nov 2006 22:37:20 +0000, Jean-David Beyer wrote this:

> noi wrote:
>
>
> To no one's surprise, traceroute does not go far.
>
> $ /usr/sbin/traceroute 172.16.4.52
> traceroute to 172.16.4.52 (172.16.4.52), 30 hops max, 38 byte packets
> 1 192.168.0.1 (192.168.0.1) 0.506 ms 0.372 ms 0.231 ms 2 * * *
> 3 * * *
> 4 * * *
> 5 * * *
> 6 * * *
> 7 * * *
> 8 * * *
>
> 192.168.0.1 is the (internal) IP address of my router. But RFC 1918,
> section 3, reserves all 172.16.*.* IP addresses to _Private Internets_. So
> it makes little difference whether my firewall or my router blocks sending
> that out. I imagine my ISP would block my trying to send to any addresses
> such as:
>
> 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 -
> 172.31.255.255 (172.16/12 prefix) 192.168.0.0 -
> 192.168.255.255 (192.168/16 prefix)
>
>
>
> DNS server is at 127.0.0.1
>
> eth2 Link encap:Ethernet HWaddr 01:02:03:04:05:06
> inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX
> packets:6397977 errors:0 dropped:0 overruns:0 frame:0 TX
> packets:3703309 errors:4 dropped:0 overruns:0 carrier:4
> collisions:0 txqueuelen:1000
> RX bytes:1219773553 (1163.2 Mb) TX bytes:483953893 (461.5 Mb)
>
>
> Destination Gateway Genmask Flags Metric Ref Use
> Iface 192.168.2.0 * 255.255.255.0 U 0 0
> 0 eth1 192.168.1.0 * 255.255.255.0 U 0 0
> 0 eth0 192.168.0.0 * 255.255.255.0 U 0 0
> 0 eth2 169.254.0.0 * 255.255.0.0 U 0 0
> 0 eth2 default 192.168.0.1 0.0.0.0 UG 0
> 0 0 eth2

You assume he's trying to ping outside of his network?

You are correct 172.16 is a class B private network but I thought, how
did he get that ip address?