From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bridging three vlans
Date: Sat, 30 Apr 2005 10:51:41 +0000 [thread overview]
Message-ID: <4273633D.1000307@wildgooses.com> (raw)
In-Reply-To: <42735BD6.3030708@wildgooses.com>
Ed Wildgoose wrote:
> OK, strange request but I want to bridge three vlans under linux 2.4.
> Bridging works fine with two vlans, but is failing to route when I add
> the third vlan.
...
> Is this a linux 2.4 limitation or user error? Grateful for any advice
Hmm, OK I know I haven't given much info, but first off is this scenario
actually possible? A bit of digging in the bridging howto suggests that
it is.
Also I just noticed that STP is off in my setup. Is this going to be
mandatory when we add three vlans into a bridge?
Thanks for any tips on actually debugging whats happening here
Ta
Ed W
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-04-30 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 10:20 [LARTC] Bridging three vlans Ed Wildgoose
2005-04-30 10:51 ` Ed Wildgoose [this message]
2005-04-30 23:22 ` Taylor, Grant
2005-05-01 10:26 ` Ed Wildgoose
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=4273633D.1000307@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@vger.kernel.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