All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirby C. Bohling" <kbohling@birddog.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Commercial Alternatives
Date: Thu, 20 Feb 2003 20:36:53 +0000	[thread overview]
Message-ID: <marc-lartc-104577354110313@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104568435724560@msgid-missing>

On Thu, 2003-02-20 at 14:24, Brad Davidson wrote:
> William L. Thomson Jr. said:
> 
> > Yes, but not in sense that traffic comes in one interface and goes out
> > another. From my understanding the main benefit of the SysMaster
> > solution was the number of connections being balanced had nothing to do
> > with the number of interfaces.
> 
> ... so it would go in and then come out again on the same interface?
> 
> I'm sure it's great as far as ease of configuration, but to tell the truth
> I'd rather plug in an extra cable or two, and not halve my available
> bandwidth by doubling the per-link traffic.
> 
> I guess it's a very targeted product, I just think it sounds rather silly.

I'm guessing it has two interfaces.  Hence the sentence:

> > Yes, but not in sense that traffic comes in one interface and goes out

The one interface connects to the local lan.  The other connects to a
network that can route to all of your upstream providers.  This way the
load balancer doesn't charge you per physical interface.  It's no harder
to load balance 2 way then 4 way, but a lot of network equipment makers
would charge you twice as much because there are twice as many
interfaces (or would charge you a significant amount more to have 4
interfaces).

I'm guessing this is a pretty smart option assuming the aggregate
traffic leaving you network is less then 100Mbit/s.  If it's more then
100Mbit/s, you can afford better equipment.  This does have some latency
and security issues, but would seem like a reasonable idea for a lot of
small networks that want to split out traffic down two providers.  If I
was a window's admin, and didn't know enought about Linux, I'd think
that was one really cool piece of equipment... *grin*.

	Thanks,
		Kirby


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-02-20 20:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 19:51 [LARTC] Commercial Alternatives Mike Nielsen
2003-02-19 22:47 ` William L. Thomson Jr.
2003-02-20 17:31 ` Brad Davidson
2003-02-20 17:41 ` John Bäckstrand
2003-02-20 18:33 ` William L. Thomson Jr.
2003-02-20 18:36 ` Brad Davidson
2003-02-20 19:56 ` William L. Thomson Jr.
2003-02-20 20:24 ` Brad Davidson
2003-02-20 20:36 ` Kirby C. Bohling [this message]
2003-02-20 21:47 ` Brad Davidson

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-104577354110313@msgid-missing \
    --to=kbohling@birddog.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.