Ethernet Bridge development
 help / color / mirror / Atom feed
From: Moire <sec@shee.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "<bridge@osdl.org> <bridge@osdl.org>" <bridge@osdl.org>
Subject: Re: [Bridge] Dead loop on virtual device - how to interpret it ?
Date: Fri, 18 Aug 2006 18:03:03 +0200	[thread overview]
Message-ID: <915e6d409ef485c793728c2b00cdc9db@shee.org> (raw)
In-Reply-To: <20060816110931.731d166d@localhost.localdomain>

Am 16.08.2006 um 20:09 schrieb Stephen Hemminger:

> On Wed, 16 Aug 2006 14:05:26 +0200
> Moire <sec@shee.org> wrote:
>>
>> i am not so familiar with the deep art of
>> network internals more with the basics one.
>> Therefore i have a problem to interpret this
>> error message:
>>
>> Dead loop on virtual device br0, fix it urgently!
>>
>> In the corresponding kernel code i found this quote:
>>
>> /* It may be transient configuration error,
>>     when hard_start_xmit() recurses. We detect
>>     it by checking xmit owner and drop the
>>     packet when deadloop is detected.
>> */
>>
>> but i still have no idea what could be wrong.

Hello,

> What are the devices you are putting in the bridge?

they exist three devices:

eth0 - Intranet
eth1  (br0) - Internet
eth2  (br0) - DMZ (public IP range)

> What kernel version?

Kernel             2.4.31
bridge-utils     1.0.4

> What are the commands being used to put the devices into
> the bridge.

My init script:

INTERFACES="eth1 eth2"
BRIDGE="br0"

do_start() {
       echo "Starting Bridge $BRIDGE"

       for interface in $INTERFACES; do
         /sbin/ip addr flush dev $interface 2>/dev/null
         /sbin/ip link set $interface up
       done

         /sbin/ip link set dev $BRIDGE down 2>/dev/null
         /sbin/brctl delbr $BRIDGE 2>/dev/null 2>/dev/null
         /sbin/brctl addbr $BRIDGE
         /sbin/brctl stp $BRIDGE off

       for interface in $INTERFACES; do
         /sbin/brctl addif $BRIDGE $interface
       done
}

> It looks like a bridge ended up including itself some how.

The system is in a production environment since two month. In that
time this message (Dead loop on virtual device br0, fix it urgently!)
appeared 5 times.  I can not reproduce this alert. Therefore i have no 
idea
what could trigger this.

One think, maybe related: I am observing packets coming from eth0
with the destination DMZ. Sometimes they are routed to the wrong
bridge port  (br0:eth1 instead br0:eth2) and consequently drop by my
iptables rules.

brctl shows

bridge name	STP enabled	interfaces
br0			no                       eth1
                                                         eth2


brctl showmacs br0 (macs are Xed)

port no	mac addr		is local?	ageing timer
    1	00:xxxxxxxxxxxx	yes		   0.00
    2	00:xxxxxxxxxxxx	no		    45.22     <<<< DMZ/Webserver
    2	00:xxxxxxxxxxxx	yes		   0.00
    1	00:xxxxxxxxxxxx	no		   0.19


Regards

C. Moire


>> My setup is an bridge (two interfaces) and local
>> interface. The bridge connects the dmz with the internet.
>>
>> How can i reproduce this error message - to find the cause.
>>
>> What does it mean (for a not so advanced admin;).


      reply	other threads:[~2006-08-18 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 12:05 [Bridge] Dead loop on virtual device - how to interpret it ? Moire
2006-08-16 18:09 ` Stephen Hemminger
2006-08-18 16:03   ` Moire [this message]

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=915e6d409ef485c793728c2b00cdc9db@shee.org \
    --to=sec@shee.org \
    --cc=bridge@osdl.org \
    --cc=shemminger@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