From: Alan Tam <Tam@SiuLung.com>
To: bridge@lists.osdl.org
Subject: [Bridge] How to disable verbose kernel logs for linux ethernet bridge?
Date: Sun, 08 May 2005 11:44:32 +0800 [thread overview]
Message-ID: <427D8B20.7010301@SiuLung.com> (raw)
Hi,
This is part of my dmesg output which is generated whenever some network
topology changes. It is very annoying. Any ways for me to inhibit those
which are only informational but not warnings which I need to take care?
I am running the all bridges on tap* interfaces emulated by OpenVPN. I
am running stock 2.6.8 kernel from Debian sarge.
Please CC me Thanks!
---8<---8<---8<---8<---8<---8<---8<---8<---8<---
br0: port 1(tap0) entering listening state
br0: port 1(tap0) entering learning state
br0: topology change detected, propagating
br0: port 1(tap0) entering forwarding state
br0: port 1(tap0) entering disabled state
device tap1 entered promiscuous mode
br0: port 2(tap1) entering listening state
br0: port 1(tap0) entering listening state
br0: port 2(tap1) entering learning state
br0: port 1(tap0) entering learning state
br0: topology change detected, propagating
br0: port 2(tap1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(tap0) entering forwarding state
eth0: no IPv6 routers present
tap0: no IPv6 routers present
br0: no IPv6 routers present
tap1: no IPv6 routers present
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: neighbor 8000.00:ff:04:c8:95:4e lost on port 1(tap0)
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, propagating
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: neighbor 8000.00:ff:05:d2:76:ca lost on port 1(tap0)
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, sending tcn bpdu
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, sending tcn bpdu
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, sending tcn bpdu
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, sending tcn bpdu
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
tap0: received packet with own address as source address
tap0: received packet with own address as source address
tap0: received packet with own address as source address
tap0: received packet with own address as source address
tap0: received packet with own address as source address
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, propagating
tap0: received packet with own address as source address
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: neighbor 8000.00:ff:05:d2:76:ca lost on port 1(tap0)
br0: port 2(tap1) entering listening state
br0: received tcn bpdu on port 1(tap0)
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering learning state
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
br0: topology change detected, propagating
br0: port 2(tap1) entering forwarding state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering blocking state
br0: neighbor 8000.00:ff:05:d2:76:ca lost on port 1(tap0)
br0: port 2(tap1) entering listening state
br0: port 2(tap1) entering learning state
br0: topology change detected, sending tcn bpdu
br0: port 2(tap1) entering forwarding state
br0: neighbor 8000.00:ff:16:cb:25:97 lost on port 2(tap1)
br0: topology change detected, propagating
---8<---8<---8<---8<---8<---8<---8<---8<---8<---
--
Regards,
Alan
next reply other threads:[~2005-05-08 3:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 3:44 Alan Tam [this message]
2005-05-09 16:59 ` [Bridge] Port link status disconnect Jorge Lanza
2005-05-09 17:50 ` Stephen Hemminger
[not found] ` <6.1.2.0.2 .20050510115447.043b4c90@luna.tlmat.unican.es>
2005-05-10 9:59 ` Jorge Lanza
2005-05-10 21:52 ` Stephen Hemminger
2005-05-11 7:36 ` Jorge Lanza
2005-05-11 16:20 ` Stephen Hemminger
2005-05-14 8:01 ` Jorge Lanza
2005-05-09 17:52 ` [Bridge] How to disable verbose kernel logs for linux ethernet bridge? Stephen Hemminger
2005-05-10 0:55 ` Alan Tam
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=427D8B20.7010301@SiuLung.com \
--to=tam@siulung.com \
--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 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.