Ethernet Bridge development
 help / color / mirror / Atom feed
From: Axel Christiansen <axel.christiansen@wlan-international.com>
To: bridge@lists.osdl.org
Subject: [Bridge] topology change on a bunch of mesh-cubes with multiple wlan interfaces
Date: Mon, 06 Sep 2004 23:02:13 +0200	[thread overview]
Message-ID: <413CD055.7040102@wlan-international.com> (raw)

Hi list,

i was searching the archiv but could not find
something matching.

In a setup with a number of mesh-cubes
(http://www.meshcube.org/) a have troble with
topology change under specific conditions.

Setup is:

The cubes are running kernel 2.4.24.
Between root and repeaters WDS is used.

root cube A
bridge br0 has interfaces:
eth0         to copper ethernet
wlan0        Managed
wlan1wds0    Repeater to cube B
wlan1wds1    Repeater to cube C

bridge cube B
bridge br0 has interfaces:
wlan0        Managed
wlan1wds0    Repeater to cube A

bridge cube C
bridge br0 has interfaces:
wlan0        Managed
wlan1wds0    Repeater to cube A

STP on
WDS auto_add off (host_ap stuff)

There are no wireless clients connected to
the network. Basicly there are 3 ethernet
links:
                                    Managed 802.11
                                              |
                                /-(2)-> bridge_cube_B
some_eth <-(1)-> root_cube_A <=
                   |            \-(3)-> bridge_cube_C
                   |                          |
              Managed 802.11        Managed 802.11

When i either turn off cube B or cube C the root
cube A gets or makes "topology change" all the time.
This takes out the interface on cube A most of the time,
making the thing completely unusable.

Today, i did a test with 4 cubes (1 root / 3 repeater)
and the oddly thing was, when taking out 1 repeater,
only one more link became unusable. So 1 link where
left operational. In the above setup all wireless
links became unusable (there are only 2, so OK).

Please let me know witch more in depth iformation
are required.

thx, Axel

                 reply	other threads:[~2004-09-06 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=413CD055.7040102@wlan-international.com \
    --to=axel.christiansen@wlan-international.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox