All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: swsnyder@home.com
Cc: Chris Wedgwood <cw@f00f.org>, linux-kernel@vger.kernel.org
Subject: Re: What does "Neighbour table overflow" message indicate?
Date: 29 Jul 2001 03:08:13 -0600	[thread overview]
Message-ID: <m11yn0cdc2.fsf@frodo.biederman.org> (raw)
In-Reply-To: <01072820231401.01125@mercury.snydernet.lan> <01072820534802.01125@mercury.snydernet.lan> <20010729135728.B3282@weta.f00f.org> <01072821151103.01125@mercury.snydernet.lan>
In-Reply-To: <01072821151103.01125@mercury.snydernet.lan>

> Further snooping shows the error msg text in file inux/net/ipv4/route.c:
> 
>     if (net_ratelimit())
>         printk("Neighbour table overflow.\n");

> 
> The reference to "net_ratelimit" make me wonder if it is related to 
> iptables.  I am using iptable, and have since kernel 2.4.1, but I've seen 
> these messages before.  Hmmm.

My experience with this is the message occurs when you a machine starts
arping for a non-existent ip address.  I suspect net_ratelimit triggers
when there are too many arps.

Run tcpdump -n -i eth0 (assuming your network is on eth0) and see if you
see an arp request that never gets answered.

Eric

  reply	other threads:[~2001-07-29  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-29  1:23 What does "Neighbour table overflow" message indicate? Steve Snyder
     [not found] ` <20010729133848.A3254@weta.f00f.org>
2001-07-29  1:53   ` Steve Snyder
2001-07-29  1:57     ` Chris Wedgwood
2001-07-29  2:15       ` Steve Snyder
2001-07-29  9:08         ` Eric W. Biederman [this message]
2001-07-29  9:46         ` Kurt Roeckx
2001-07-29 13:55         ` Bernd Eckenfels
2001-07-30 12:38     ` Carlos O'Donell Jr.
2001-07-30 23:28       ` Rob Landley
2001-07-29  5:41 ` Riley Williams
2001-07-29 13:50   ` jeff millar

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=m11yn0cdc2.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swsnyder@home.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.