Skip to contentSkip to conversation

How to disable verbose kernel logs for linux ethernet bridge?

Bridge Alan Tam 3 participants 10 messages May 8, 2005 – May 14, 2005 1 message not in the archive Ethernet bridge

lore
Share & tools
lore

Alan Tam

author
#0 lore 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<---

Signature · 2 lines
Regards,
Alan
#1 lore raw

[Bridge] Port link status disconnect

Hi all.

I have been working with bridges on kernel 2.4.X but now I have upgrade to kernel 2.6.11 and the behaviour seems to be different. I face problem when I include a wireless device as in /var/log/messages I get (3-5) which before I didn't.

1)May  5 10:53:01 fuj1 kernel: br0: topology change detected, propagating
2)May  5 10:53:01 fuj1 kernel: br0: port 2(eth2) entering forwarding state
3)May  5 10:53:06 fuj1 kernel: eth2: New link status: Disconnected (0002)
4)May  5 10:53:06 fuj1 kernel: ip_tables: (C) 2000-2002 Netfilter core team
5)May  5 10:53:07 fuj1 kernel: eth2: New link status: Connected (0001)
6)May  5 10:53:20 fuj1 kernel: br0: port 2(eth2) entering disabled state

Lets explain the steps I follow. Brigde ports --- eth1 wired interface eth2 wireless interface
To set up the bridge and include both ports I run the following.

brctl addbr br0
brctl addif br0 eth1
brctl addif br0 eth2
ifconfig eth1 0.0.0.0
ifconfig eth2 0.0.0.0
ifconfig br0 10.0.1.4 up

As you can see I set the eth2 ip address to 0.0.0.0. However after a while the eth2 returns by it self to the previous configured IP address (i.e. 128.0.1.50). So, in order to make things work in the correct way I have to retype ifconfig eth2 0.0.0.0 and the second time seems that everything works as expected and the eth2 doesn't go back to the previous state.

Why does it happen? What can I do? I need the device not to "get out of the brigde" and reconfigured. I have try to brctl br0 setfd 0 but still have the same problem.

Any help is really welcomed.

TA.

#2 lore raw

Re: [Bridge] Port link status disconnect

Quoted 32 lines · On Mon, 09 May 2005 18:59:54 +0200 Jorge Lanza <[email protected]> wrote:

Hi all.

I have been working with bridges on kernel 2.4.X but now I have upgrade to kernel 2.6.11 and the behaviour seems to be different.
I face problem when I include a wireless device as in /var/log/messages I get (3-5) which before I didn't.

1)May  5 10:53:01 fuj1 kernel: br0: topology change detected, propagating
2)May  5 10:53:01 fuj1 kernel: br0: port 2(eth2) entering forwarding state
3)May  5 10:53:06 fuj1 kernel: eth2: New link status: Disconnected (0002)
4)May  5 10:53:06 fuj1 kernel: ip_tables: (C) 2000-2002 Netfilter core team
5)May  5 10:53:07 fuj1 kernel: eth2: New link status: Connected (0001)
6)May  5 10:53:20 fuj1 kernel: br0: port 2(eth2) entering disabled state

Lets explain the steps I follow. Brigde ports --- eth1 wired
interface eth2 wireless interface
To set up the bridge and include both ports I run the following.

brctl addbr br0
brctl addif br0 eth1
brctl addif br0 eth2
ifconfig eth1 0.0.0.0
ifconfig eth2 0.0.0.0
ifconfig br0 10.0.1.4 up

As you can see I set the eth2 ip address to 0.0.0.0. However after a while the eth2 returns by it self to the previous configured IP address (i.e. 128.0.1.50). So, in order to make things work in the correct way I have to retype ifconfig eth2 0.0.0.0 and the second time seems that everything works as expected and the eth2 doesn't go back to the previous state.

Quoted 4 lines

Why does it happen? What can I do? I need the device not to "get out of the brigde" and reconfigured. I have try to brctl br0 setfd 0 but still have the same problem.

Probably you have eth2 configured in the normal distribution network configuration and the hotplug scripts are detecting the transition and setting it back.

You need to make sure eth interfaces are not configured by other means.

#8 lore raw
In reply to Alan Tam
Quoted 11 lines · On Sun, 08 May 2005 11:44:32 +0800 Alan Tam <[email protected]> wrote:

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!

The easiest way would be to change all those printk's you don't want to see in the br_stp_if.c from:

	printk(KERN_INFO "%s: port ...
to
	printk(KERN_DEBUG "%s: port ...

then they will show up only in /var/log/messages.

author
#9 lore raw
Quoted 7 lines · Stephen Hemminger
Quoted 3 lines · On Sun, 08 May 2005 11:44:32 +0800 Alan Tam <[email protected]> wrote:

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.

Quoted 9 lines

The easiest way would be to change all those printk's you don't want to see in the br_stp_if.c from:

	printk(KERN_INFO "%s: port ...
to
	printk(KERN_DEBUG "%s: port ...

then they will show up only in /var/log/messages.

Yes, but recompiling the kernel is not a good thing to me. I think "echo 5 > /proc/sys/kernel/printk" is acceptable. The reason it isn't the default is probably that most part of the kernel won't be so verbose.

Signature · 2 lines
Regards,
Alan
#3 lore raw

Re: [Bridge] Port link status disconnect

In reply to Stephen Hemminger
Quoted 14 lines · Stephen Hemminger
Quoted 11 lines · On Mon, 09 May 2005 18:59:54 +0200 Jorge Lanza <[email protected]> wrote:

As you can see I set the eth2 ip address to 0.0.0.0. However after a while the eth2 returns by it self to the previous configured IP address (i.e. 128.0.1.50). So, in order to make things work in the correct way I have to retype ifconfig eth2 0.0.0.0 and the second time seems that everything works as expected and the eth2 doesn't go back to the previous state.

Why does it happen? What can I do? I need the device not to "get out of the brigde" and reconfigured. I have try to brctl br0 setfd 0 but still have the same problem.

Quoted 5 lines

Probably you have eth2 configured in the normal distribution network configuration
and the hotplug scripts are detecting the transition and setting it back.

You need to make sure eth interfaces are not configured by other means.

Thanks very much, but the problem now is that I don't understand how to do what you tell me. Could you give me some hints on it? It would be grateful if you could do so.

TA.

#4 lore raw

Re: [Bridge] Port link status disconnect

Quoted 21 lines · On Tue, 10 May 2005 11:59:48 +0200 Jorge Lanza <[email protected]> wrote:
Quoted 10 lines · Stephen Hemminger
Quoted 8 lines · On Mon, 09 May 2005 18:59:54 +0200 Jorge Lanza <[email protected]> wrote:

As you can see I set the eth2 ip address to 0.0.0.0. However after a while the eth2 returns by it self to the previous configured IP address (i.e. 128.0.1.50). So, in order to make things work in the correct way I have to retype ifconfig eth2 0.0.0.0 and the second time seems that everything works as expected and the eth2 doesn't go back to the previous state.

Why does it happen? What can I do? I need the device not to "get out of

the

Quoted 8 lines
Quoted 3 lines

brigde" and reconfigured. I have try to brctl br0 setfd 0 but still have the same problem.

Probably you have eth2 configured in the normal distribution network configuration
and the hotplug scripts are detecting the transition and setting it back.

Quoted 5 lines
Quoted 1 line

You need to make sure eth interfaces are not configured by other means.

Thanks very much, but the problem now is that I don't understand how to do what you tell me.
Could you give me some hints on it? It would be grateful if you could do so.

What distribution of linux are you using? Redhat, Fedora, Debian, Suse?

#5 lore raw

Re: [Bridge] Port link status disconnect

Quoted 1 line · Stephen Hemminger

What distribution of linux are you using? Redhat, Fedora, Debian, Suse?

I'm using Fedora Core 3

Thanks

#6 lore raw

Re: [Bridge] Port link status disconnect

Quoted 4 lines · On Wed, 11 May 2005 09:36:03 +0200 Jorge Lanza <[email protected]> wrote:
Quoted 1 line · Stephen Hemminger

What distribution of linux are you using? Redhat, Fedora, Debian, Suse?

I'm using Fedora Core 3

Then you need to go into:
Applications -> System Tools -> Network Device Control Configure
Select device then hit Edit

Uncheck the box "Activate this device when computer starts"

or edit /etc/sysconfig/network-scripts/ifcfg-eth0 (assuming it is eth0)
and change ONBOOT=yes to ONBOOT=no

#7 lore raw

Re: [Bridge] Port link status disconnect

Still having the same problem ;) Seems not to work well. I will give another try.

Any other posible solution ??

TA.

Quoted 13 lines · Stephen Hemminger
Quoted 4 lines · On Wed, 11 May 2005 09:36:03 +0200 Jorge Lanza <[email protected]> wrote:
Quoted 1 line · Stephen Hemminger

What distribution of linux are you using? Redhat, Fedora, Debian, Suse?

I'm using Fedora Core 3

Then you need to go into:
Applications -> System Tools -> Network Device Control Configure
Select device then hit Edit

Quoted 6 lines

Uncheck the box "Activate this device when computer starts"

or edit /etc/sysconfig/network-scripts/ifcfg-eth0 (assuming it is eth0)
and change ONBOOT=yes to ONBOOT=no

--------------------------------------------

Jorge Lanza Calderón
Departamento Ingeniería Comunicaciones
Grupo de Ingeniería Telemática
Universidad de Cantabria
Avda. de los Castros, s/n
39005 - Santander (España)
Tel: +34 942 200914
Fax: +34 942 201488
mailto:[email protected]
Web: http://www.tlmat.unican.es

--------------------------------------------