From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: Gabor Juhos <juhosg@openwrt.org>, bloat-devel@lists.bufferbloat.net
Subject: Re: Hacking on the rtl8366S
Date: Fri, 03 Jun 2011 14:42:33 +0200 [thread overview]
Message-ID: <7i39jr3x3a.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <BANLkTinLFyEukrLy3JSZi+HVz45OTJubEw@mail.gmail.com> (Dave Taht's message of "Fri, 3 Jun 2011 06:28:31 -0600")
> (the switch is bridged to the wireless interfaces, normally)
Are you sure about that? The usual configuration is to use a hardware
switch between the wired ports, but bridge the wired and wireless ports
in software. Can you post the output of brctl show?
At any rate, you should be able to program the switch to put each port
on a different vlan -- that's how the separation between LAN and WAN
ports is usually implemented.
-- Juliusz
next prev parent reply other threads:[~2011-06-03 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 12:28 Dave Taht
2011-06-03 12:42 ` Juliusz Chroboczek [this message]
2011-06-03 14:32 ` Dave Taht
2011-06-04 3:49 ` Dave Taht
2011-06-04 3:54 ` Dave Taht
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=7i39jr3x3a.fsf@lanthane.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=juhosg@openwrt.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