From: "Alonso Enero V." <alonso.enero@gmail.com>
To: bridge@lists.osdl.org, bridge@siennax.com
Subject: [Bridge] bridge - canopy - cisco catalyst 2950
Date: Fri, 10 Nov 2006 18:54:49 -0300 [thread overview]
Message-ID: <4554f533.18d37d8d.5d69.ffffc5a2@mx.google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]
Hi Friends!
Sorry for disturb you.
I want to ask you something about a bridge implementation that I
need to make work.
This implementation uses Motorola Canopy (a wireless
implementation) to link two sites of my work company backing up an optic
fiber link (the main link) like appears in the following picture:
Everything works ok in a laboratory environment, without the Cisco
Catalyst switch, but when link the #1 bridge to the Cisco Catalyst
respective port (the one with the needed VLAN), starts a horrible loop in
our LAN. I think something happens inside the Cisco switch that difficult
the STP traffic between the #1 bridge and out site 3. I heard of something
called bdpufilter, which is not set in out Catalyst switch, said our ISP. I
read a page were you give some suggestions of tweak the Linux Kernel that I
did (http://lists.osdl.org/pipermail/bridge/2005-October/001116.html), but
still didn't tested, until have a clear idea of what happens inside the
Cisco switch.
Thanks in advice!
Alonso Enero V.
<mailto:alonso.enero@gmail.com> alonso.enero@gmail.com
Santiago, Chile
[-- Attachment #1.2: Type: text/html, Size: 7668 bytes --]
[-- Attachment #2: image002.jpg --]
[-- Type: image/jpeg, Size: 85265 bytes --]
next reply other threads:[~2006-11-10 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 21:54 Alonso Enero V. [this message]
2006-11-10 22:33 ` [Bridge] bridge - canopy - cisco catalyst 2950 Stephen Hemminger
2006-11-13 22:57 ` Melissa Meyer
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=4554f533.18d37d8d.5d69.ffffc5a2@mx.google.com \
--to=alonso.enero@gmail.com \
--cc=bridge@lists.osdl.org \
--cc=bridge@siennax.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.