From: Rodolfo Giometti <giometti@enneenne.com>
To: "Srinivas M.A." <srinivas.aji@gmail.com>
Cc: bridge@lists.linux-foundation.org, Gianpietro Germi <g.germi@selta.it>
Subject: Re: [Bridge] Invalid BPDU transmission?
Date: Wed, 6 Oct 2010 17:32:32 +0200 [thread overview]
Message-ID: <20101006153232.GC24438@enneenne.com> (raw)
In-Reply-To: <AANLkTim1o6SVjV76A5b2zho-HpPjeDqU8ZyAw55GNMjQ@mail.gmail.com>
On Tue, Oct 05, 2010 at 06:10:32PM +0530, Srinivas M.A. wrote:
> Both CONFIG and TCN BPDUs are used only in STP compatibility mode. In
> RSTP mode, the BPDUs sent in both directions are RSTP BPDUs. So they
> can be sent on the root port.
>
> For a description of how topology changes are handled, see the section
> titled "New Topology Change Mechanisms" in
> http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml
>
> Is this causing any particular issue?
Yes. By using the following connection:
+---------------+ +----------------------+
| EXTRA bridge O <----> O(eth5) bridge on test |
+---------------+ | (eth0) (eth1) |
+--------O------O------+
^ ^
| |
+------+
where «EXTRA bridge» is a rstp bridge acting as root bridge and NOT
running rstpd (but a proprietary rstp implementation), while «bridge
on test» is my bridge running rstpd.
«EXTRA bridge» sends to «bridge on test» the following BDPU:
01 80 c2 00 00 00 00 02 3e 99 ba 1c 00 27 42 42
03 00 00 02 02 7e 80 00 00 02 3e 99 ba 1c 00 00
00 00 80 00 00 02 3e 99 ba 1c 80 01 00 00 14 00
02 00 0f 00 00
and «bridge on test» replies on «eth5», which is its root port.
Without my modification «bridge on test» is unstable, in fact the
states of eth0 and eth1 ports doesn't fit to Fwd end Blk but they
change in a strange manner and don't stabilize... also opening and
closing the loop cause more instability and the bridge takes very long
time before changing its ports states!
By adding my modification everything works well.
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
next prev parent reply other threads:[~2010-10-06 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 9:54 [Bridge] Invalid BPDU transmission? Rodolfo Giometti
2010-10-05 12:40 ` Srinivas M.A.
2010-10-06 15:32 ` Rodolfo Giometti [this message]
2010-10-06 16:20 ` Rodolfo Giometti
2010-10-06 21:51 ` Srinivas M.A.
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=20101006153232.GC24438@enneenne.com \
--to=giometti@enneenne.com \
--cc=bridge@lists.linux-foundation.org \
--cc=g.germi@selta.it \
--cc=srinivas.aji@gmail.com \
/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.