All of lore.kernel.org
 help / color / mirror / Atom feed
From: Melissa Meyer <melissa@volunteermatch.org>
To: "Alonso Enero V." <alonso.enero@gmail.com>
Cc: bridge@lists.osdl.org, bridge@siennax.com
Subject: Re: [Bridge] bridge - canopy - cisco catalyst 2950
Date: Mon, 13 Nov 2006 14:57:49 -0800	[thread overview]
Message-ID: <4558F86D.6010504@volunteermatch.org> (raw)
In-Reply-To: <4554f533.18d37d8d.5d69.ffffc5a2@mx.google.com>



Did you get an answer to this?

I had a similar experience. To fix, I had to turn off spanning tree on 
the cisco switch connected to the bridges as well as turn on dot1q 
trunking on the ports on the switch the bridges used.

So the cisco config for my bridge ports:

switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate

For the other ports on the switch, the switchport mode was set to access.

Hope this helps.



Alonso Enero V. wrote:
>
> 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.
>
> alonso.enero@gmail.com <mailto:alonso.enero@gmail.com>
>
> Santiago, Chile
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>   

      parent reply	other threads:[~2006-11-13 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 21:54 [Bridge] bridge - canopy - cisco catalyst 2950 Alonso Enero V.
2006-11-10 22:33 ` Stephen Hemminger
2006-11-13 22:57 ` Melissa Meyer [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=4558F86D.6010504@volunteermatch.org \
    --to=melissa@volunteermatch.org \
    --cc=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.