Can't ping but can surf the web[SOLVED] Not system fault

[dalek]

I'm sure I missed something somewhere here but I had some Kppp problems lately and was trying to use ping. I can surf with Mozilla and get email with Kmail and emerge just fine, download that is. I can not get any pings out. I can ping the local host, 127.0.0.1, but nothing else. This is what I get:

[adaptr]

What do you have in /etc/resolv.conf?
Do you use a proxy for surfing ?
Do you run a local nameserver ?

This is a dns misconfiguration - either at your end or the ISP.

[dalek]

Info alert.

resolv.conf

search smoker local

# ppp temp entry
nameserver 205.216.82.2 # ppp temp entry
nameserver 208.231.96.12 # ppp temp entry
nameserver 205.216.82.2 #kppp temp entry
nameserver 208.231.96.12 #kppp temp entry

If there is a proxy running, I don't know about it. Probably not.

Don't know about a local namserver either. Well except for the bit in resolv.conf up above.

I read somewhere that some were starting to 'block' ping for security reasons. I don't remember where or know if it affects this.

I can boot into Mandrake and see if it works there if you need me to. I also followed the install guide for the relavent stuff. I am on dial-up.

Thanks for the help. Any ideas from that?


_________________
My rig: Gigabyte GA-970A-UD3P mobo, AMD FX-8350 Eight-Core CPU, ZALMAN CNPS10X Performa CPU cooler,
G.SKILL 32GB DDR3 PC3 12800 Memory Nvidia GTX-650 video card LG W2253 Monitor
60TBs of hard drive space using LVM
Cooler Master HAF-932 Case

[supenguin]

I'd ask your ISP if they are blocking ping/icmp packets. Mine started doing that with Slammer or some nasty Microsoft worm. It was pinging everything in sight looking for hosts to infect, and was causing some massive network slowdowns. Took them a few months to turn it back on.

You may want to check the man page on ping. I think there's some way to make it use TCP/IP packets instead of ICMP so it'll get by those blocks. Oh, and traceroute uses ICMP packets also, so it'll have the same issues and the same workaround.

If that's not it, I don't know what the problem is.
_________________
We don't need no stinkin' signatures.

[LinuxTechie]

I work for a web hosting company and we had to block ICMP traffic, and here is the Network Status that we put out...

ICMP traffic coming in to our network has been blocked in efforts to defend against a new worm that has been unleashed on the internet. Because of this, clients will be unable to ping our network, traceroute may be effected. More information about the worm can be found here:
http://isc.sans.org/diary.html?date=2003-08-18

However, try traceroute because on our network ping is affected, but traceroute (from a Linux box) is not affected but from a Windows box it will not work. I was told that Windows uses ICMP for traceroute and Linux uses UDP, but am unsure if that is true about the UDP thing. Maybe a different type of ICMP packet, because I know we only blocked the one the worm was using.

Example:

My Windows machine to my domain on my works network:

C:\Documents and Settings\Michael Martin>tracert techiecenter.com

Tracing route to techiecenter.com [66.34.32.78]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.123.254
2 28 ms 10 ms 10 ms 10.176.208.1
3 20 ms 10 ms 10 ms 12.244.112.65
4 13 ms 13 ms 11 ms 12.244.69.5
5 12 ms 17 ms 36 ms 12.244.69.1
6 12 ms 20 ms 12 ms 12.119.124.149
7 11 ms 11 ms 11 ms gbr2-p50.dlstx.ip.att.net [12.123.16.238]
8 12 ms 11 ms 13 ms tbr2-p012701.dlstx.ip.att.net [12.122.12.81]
9 30 ms 11 ms 12 ms ggr1-p380.dlstx.ip.att.net [12.122.12.94]
10 12 ms 12 ms 13 ms att-gw.sf.cw.net [192.205.32.226]
11 18 ms 21 ms 13 ms 64.245.102.62
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

From my Linux box:

[root@budlight ~] $ traceroute techiecenter.com
traceroute to 66.34.32.78 (66.34.32.7, 30 hops max, 40 byte packets
1 192.168.123.254 (192.168.123.254) 1.190 ms 1.177 ms 1.293 ms
2 * 10.176.208.1 (10.176.208.1) 18.989 ms 9.925 ms
3 12.244.112.65 (12.244.112.65) 12.356 ms 11.692 ms 10.723 ms
4 12.244.69.5 (12.244.69.5) 10.110 ms 9.368 ms 14.707 ms
5 12.244.69.1 (12.244.69.1) 11.186 ms 12.706 ms 11.763 ms
6 12.119.124.149 (12.119.124.149) 10.145 ms 17.787 ms 11.896 ms
7 gbr2-p50.dlstx.ip.att.net (12.123.16.238) 11.455 ms 15.210 ms 11.988 ms
8 tbr2-p012701.dlstx.ip.att.net (12.122.12.81) 11.929 ms 14.303 ms 13.933 ms
9 ggr1-p380.dlstx.ip.att.net (12.122.12.94) 10.888 ms 12.622 ms 14.381 ms
10 att-gw.sf.cw.net (192.205.32.226) 11.934 ms 46.980 ms 11.631 ms
11 64.245.102.62 (64.245.102.62) 54.946 ms 53.010 ms 15.273 ms
12 66.34.32.78 (66.34.32.7 14.092 ms 19.526 ms 35.395 ms
[root@budlight ~] $

[dalek]

That is what I was thinking. It may be my ISP's ISP that is blocking.

On the other question, I get this:

bash-2.05b# traceroute www.google.com
bash: traceroute: command not found
bash-2.05b# whois www.google.com
bash: whois: command not found
bash-2.05b#

What do I need to download to get these to work?

I got this from emerge search who

[LinuxTechie]

root@machine# emerge traceroute whois

[LinuxTechie]

fyi, you can leave out the www in www.google.com.

traceroute/whois google.com is sufficient. Just trying to save you some keystrokes

[dalek]