All of lore.kernel.org
 help / color / mirror / Atom feed
From: ro0ot <ro0ot@phreaker.net>
To: netfilter@lists.netfilter.org
Subject: Neighbour table overflow
Date: Wed, 05 Jan 2005 08:42:32 +0800	[thread overview]
Message-ID: <41DB37F8.6020709@phreaker.net> (raw)

Hi,

I had setup my bridge (br0) as below: -

ifconfig eth0 0.0.0.0
ifconfig eth5 0.0.0.0

brctl addbr br0

brctl addif br0 eth0
brctl addif br0 eth5

brctl stp br0 on

ifconfig br0 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255

I had my firewall scripts setup correctly.

Once I connect both the interface (eth0 and eth5) to my network.  I 
can't ping to my router (connect to eth0) or ping to my other IP 
addresses (connect to eth5).  I check around and found out some messages 
pops up in /var/log/syslog file as below: -

Jan  2 10:44:22 fw01 kernel: ipt_tcpmss_target: bad length (64 bytes)
Jan  2 10:44:32 fw01 last message repeated 11 times
Jan  2 12:27:08 fw01 kernel: Neighbour table overflow.
Jan  2 12:27:11 fw01 last message repeated 9 times
Jan  2 12:27:13 fw01 kernel: NET: 10 messages suppressed.
Jan  2 12:27:13 fw01 kernel: Neighbour table overflow.
Jan  2 12:27:18 fw01 kernel: NET: 27 messages suppressed.
Jan  2 12:27:18 fw01 kernel: Neighbour table overflow.

Once I disconnect the cable from the eth5 interface, I can ping to my 
router.  I try to reconnect the cable back to the eth5 interface and run 
a ping to my router.  As the result, I can't ping the router and the 
similar messages pops up in the /var/log/syslog file.

How can I resolve this issue?

Regards,
ro0ot






             reply	other threads:[~2005-01-05  0:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  0:42 ro0ot [this message]
2005-01-05  2:25 ` Neighbour table overflow Jason Opperisano
  -- strict thread matches above, loose matches on Subject: below --
2005-03-23 14:08 Sebastiao Antonio Campos (GWA)
2005-03-23 14:23 ` Jason Opperisano
2004-10-28  2:25 John Pearson
2004-10-26 17:39 Dominik Karall
2004-10-26 21:23 ` Chris Wedgwood
2004-10-26 22:10   ` Dominik Karall
2004-10-26 21:52 ` Ernst Herzberg
2004-10-26 22:11   ` Dominik Karall
2004-10-26 23:06     ` David S. Miller
2004-10-26 23:58       ` Wichert Akkerman
2004-10-27  0:30       ` Dominik Karall
2002-11-26 14:40 more than 1 source ip Ben Russo
2002-11-26 18:39 ` Neighbour table overflow g_netfilter
2002-11-26 18:38   ` Ard van Breemen
2002-11-28 16:40     ` Roberto Nibali
2002-11-27  4:08   ` Arnt Karlsen
2001-01-22 14:38 Daniel Furse
2001-01-22 15:22 ` Wolfgang Denk
2001-01-22 11:33 Daniel Furse

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=41DB37F8.6020709@phreaker.net \
    --to=ro0ot@phreaker.net \
    --cc=netfilter@lists.netfilter.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 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.