From: Hampton Maxwell <maxwell@digitalpath.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Rewriting output interface
Date: Mon, 29 Jan 2007 22:14:25 +0000 [thread overview]
Message-ID: <45BE71C1.2090206@digitalpath.net> (raw)
I would like to setup some rules for a wireless bridge to do load balancing.
I'd like to dedicate one radio for doing transmit and one for receive.
router
|
|
------------- eth0 ----------------
| |
wlan0 upstream device wlan1
| ^
| |
V ============= ^
| |
V |
wlan2 downstream device wlan3
| |
------------- eth0 ----------------
|
|
network
All traffic headed to the network will be sent out on wlan0, while all
traffic headed to the router to be sent on wlan3. Is tc capable of doing
something like this, and if so, how would I configure it? I would prefer to
bridge the traffic rather than routing it.
Thanks,
Hampton
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-01-29 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 22:14 Hampton Maxwell [this message]
2007-01-29 22:41 ` [LARTC] Rewriting output interface Hampton Maxwell
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=45BE71C1.2090206@digitalpath.net \
--to=maxwell@digitalpath.net \
--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 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.