From: "William L. Thomson Jr." <support@obsidian-studios.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why multiple NICs in a multiple route situation?
Date: Fri, 02 Aug 2002 07:57:26 +0000 [thread overview]
Message-ID: <marc-lartc-102827517501253@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102827313732464@msgid-missing>
Greg,
On Fri, 2002-08-02 at 00:46, Greg Scott wrote:
> 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:.
>
> 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?
Please someone correct me if I am wrong.
To my knowledge ethernet does mostly broadcasting. So the traffic from
one router will be bounced off both.
If one says hello I am this ip, the other will say it's ip, until the
proper path is determined.
It's kind of like the difference between a switch and a hub, sort of.
I would recommend trying to isolate the traffic from each to the Linux
router if possible, using a nic per connection/router. With dual or
multiple port nic cards it's not so much of an issue.
Even though the nic is on the Linux side will be 100mbit, most routers
are only 10mbit, so the broadcast flooding could become an issue.
Also in order to use a single nic with multiple connections another
device like a switch or a hub will have to be inline. Which will create
another hop.
So for that reason alone it's worth having two nics, or at least a port
per connection/router.
So for example in my case I do
Router1 --| | |-- Server
| Linux Router |-- Switch --|-- Server
Router2 --| | |-- Server
Otherwise you will have to have two switches or hubs. I mean how can you
connect two devices to one ethernet port?
So two reasons I can think of are:
1. To isolate broadcasts from each router
2. To reduce hops to the Linux Router
I really can't think of any other reason.
Maybe someone else can?
--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone 707.766.9509
Fax 707.766.8989
http://www.obsidian-studios.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-02 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 7:46 [LARTC] Why multiple NICs in a multiple route situation? Greg Scott
2002-08-02 7:57 ` William L. Thomson Jr. [this message]
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-102827517501253@msgid-missing \
--to=support@obsidian-studios.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.