From: ro0ot <ro0ot@phreaker.net>
To: bridge@lists.osdl.org
Subject: [Bridge] 1 system with 3 bridges
Date: Mon, 16 Jan 2006 23:09:29 +0800 [thread overview]
Message-ID: <43CBB729.9030007@phreaker.net> (raw)
Hi all,
I have one bridge system (used for controlling bandwidth) connected to
three different DSL ISP provider. I have the following setup below: -
+-------------+
| br0 |
| -> eth1 | -> DSL_1
| -> eth2 |
+-------------+
| br1 |
| -> eth3 | -> DSL_2
| -> eth4 |
+-------------+
| br2 |
| -> eth5 | -> DSL_3
| -> eth6 |
+-------------+
br0 has eth1 and eth2; br0 has no ip address
br1 has eth3 and eth4; br0 has no ip address
br2 has eth5 and eth6; br0 has no ip address
The traffic of DSL_1 ISP will pass thru br0. The traffic of DSL_2 ISP
will pass thru br1. The traffic of DSL_3 ISP will pass thru br2.
I have a question. Is it ok I do it as above in 1 system with 3 bridges
or separate it to 3 system with each system have their own bridge?
Regards,
ro0ot
next reply other threads:[~2006-01-16 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 15:09 ro0ot [this message]
2006-01-16 16:27 ` [Bridge] 1 system with 3 bridges Stephen Hemminger
2006-01-16 16:00 ` ro0ot
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=43CBB729.9030007@phreaker.net \
--to=ro0ot@phreaker.net \
--cc=bridge@lists.osdl.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.