From: "Greg Scott" <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Why multiple NICs in a multiple route situation?
Date: Fri, 02 Aug 2002 07:46:17 +0000 [thread overview]
Message-ID: <marc-lartc-102827313732464@msgid-missing> (raw)
In a situation with multiple routers to the Internet and a
Linux firewall/router that either makes a choice about which
route to use or load balances among the routes:
> I don't think you *need* to have a separate NIC for each
> router, but if I were doing it, I'd want each router on a
> separate network.
This has been bugging me - if a single NIC will work then what
value does another NIC add? Let's say the circuits are both T1.
With two possible circuits, that's just a little more than 3mb
per second. At 100 mbit per NIC, it would take more than 50
T1s to swamp it.
So why a NIC per T1? Why not just give a single NIC an
IP address in all the networks for each T1? Or am I missing
something important?
thanks
- Greg Scott
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-08-02 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 7:46 Greg Scott [this message]
2002-08-02 7:57 ` [LARTC] Why multiple NICs in a multiple route situation? William L. Thomson Jr.
2002-08-06 16:30 ` Michael T. Babcock
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=marc-lartc-102827313732464@msgid-missing \
--to=gregscott@infrasupportetc.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 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.