From: ro0ot <ro0ot@phreaker.net>
To: bridge@lists.osdl.org
Subject: [Bridge] Neighbour table overflow.
Date: Wed, 05 Jan 2005 01:50:32 +0800 [thread overview]
Message-ID: <41DAD768.8020800@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
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
next reply other threads:[~2005-01-04 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 17:50 ro0ot [this message]
2005-01-04 18:26 ` [Bridge] Neighbour table overflow Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 17:39 WL Siew
2005-01-04 20:30 ` Christopher E. Cramer
2005-01-04 21:04 ` Bart De Schuymer
2005-01-05 0:40 ` ro0ot
2005-01-05 14:10 ` ro0ot
2005-01-06 21:56 ` Stephen Hemminger
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=41DAD768.8020800@phreaker.net \
--to=ro0ot@phreaker.net \
--cc=bridge@lists.osdl.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