ICMP Ping being lost between kernel and the ping program.

From: Jesse Gordon (jesseg_at_nikola.com)
Date: 11/16/05

  • Next message: Constantine Gavrilov: "gcc optimizer miscompiles code with sigaddset on i386 ?" 
    To: <linux-kernel@vger.kernel.org>
Date:	Wed, 16 Nov 2005 12:23:27 -0800

    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!

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Constantine Gavrilov: "gcc optimizer miscompiles code with sigaddset on i386 ?"

    Relevant Pages

    • Re: Wireless Network in Public Places Options
      ... >which are running mostly WRT54G hardware with alternative firmware. ... >which VLAN the packets need to stay inside. ... >with wireless as it cuts down on excessive broadcast traffic. ... But I was assuming that you understood that ping uses ...
      (microsoft.public.win2000.networking)
    • Re: Wireless Network in Public Places Options
      ... >which are running mostly WRT54G hardware with alternative firmware. ... >which VLAN the packets need to stay inside. ... >with wireless as it cuts down on excessive broadcast traffic. ... But I was assuming that you understood that ping uses ...
      (microsoft.public.win2000.networking)
    • Re: ping time out trouble , help
      ... Ping packets get lost discontinuously. ... whether there is any device in the scope that interfere the wireless. ... please also check how it works if you PING with small MTU. ...
      (microsoft.public.windows.server.sbs)
    • Netgear MA401 stopped working
      ... the host, seem to be sending packets, but never receive anything back. ... PING 192.168.112.1: 56 data bytes ... I, on the other hand, suspect a hardware problem with the card. ... pci_cfgintr: 0:2 INTA BIOS irq 11 ...
      (freebsd-net)
    • ipw-firmware (Intel Pro/Wireless 2100 Driver) Help
      ... I see lots of wireless networks around my ... ipw0 scan, nothing shows up. ... ping: cannot resolve www.google.com: Host name lookup failure ... 133 packets transmitted, 0 packets received, 100% packet loss ...
      (freebsd-net)