public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jesse Gordon" <jesseg@nikola.com>
To: <linux-kernel@vger.kernel.org>
Subject: ICMP Ping being lost between kernel and the ping program.
Date: Wed, 16 Nov 2005 12:23:27 -0800	[thread overview]
Message-ID: <009401c5eaeb$9a77be00$5e00800a@printserver> (raw)
In-Reply-To: 200511161252.08927.bjorn.helgaas@hp.com

Greetings. This is my first post.

I'm having a weird intermittent problem with ping.

I'm pinging the WAN port of a cheap home DSL firewall (d-link di-604) and 
sometimes the ping program fails to get a response,
but if I run tcpdump I can see that the response is indeed coming back.

arping on the target IP always works.

We're a small wireless ISP with 40ish customers -- each of whom has a cheap 
dlink router at their home. We ping each of them regularly to be notified of 
a wireless loss of connection.
(The wireless is Trango running at 5.x Ghz or ~900Mhz -- not 802.11) and all 
the wireless and switches are just ethernet bridges -- so it's a flat 
network with no ip based routing.

Two different dlink routers cause this problem but not necisarly at the same 
time.

Two different Linux computers exhibit this problem, although again, not 
always at the same time. One seems to be more picky -- sometimes just the 
picky one has a problem, other times they both have the problem.

Also, I have not yet noticed this problem while pinging from a windows 
computer.

Picky one:Linux 2.4.26
Less picky one: Linux 2.6.11.11 SMP

Anyhow, I don't know whether the dlinks are sometimes sending out sligly 
malformed packets, whether they are getting slightly damaged over the 
wireless network,
or whether Linux [the kernel] is having a problem, or if the ping program is 
having the problem. The facts just don't make sense for any of those.

I'll be glad to do all the normal stuff -- upgraded to latest kernel, (I did 
try upgrading to latest ping not too long ago no help - can try again),  if 
anyone thinks that'll help me solve the mystery.
I can even capture the text description of or the raw contents of packets 
with tcpdump or maybe ethereal, if that will help.

I did one time capture with ethereal a packet when ping was working, then a 
packet when it wasn't and compared them side by side in two ethereal 
instances -- and aside from the fields that should have been different, 
everything looked the same.

Thanks! 



  reply	other threads:[~2005-11-16 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 21:16 [RESEND] [PATCH] drivers/acpi/asus_acpi.c unsigned comparison Gabriel A. Devenyi
2005-11-16 19:52 ` Bjorn Helgaas
2005-11-16 20:23   ` Jesse Gordon [this message]
2005-11-17 21:35     ` ICMP Ping being lost between kernel and the ping program. (Solved!) Jesse Gordon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009401c5eaeb$9a77be00$5e00800a@printserver' \
    --to=jesseg@nikola.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox