Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Sven Schuster <schuster.sven@gmx.de>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: 2 NICs on same subnet
Date: Fri, 05 Nov 2004 10:32:38 -0500	[thread overview]
Message-ID: <1099668758.4891.114.camel@localhost> (raw)
In-Reply-To: <20041105142219.GB12563@zion.homelinux.com>

On Fri, 2004-11-05 at 09:22, Sven Schuster wrote:
> Hi Marc,
> 
> On Fri, Nov 05, 2004 at 02:04:24PM +0100, Marc Haber told us:
> > What you intend to do does not make sense.
> >
> > This surely is meant to be a solution to some unmentioned problem. By
> > asking about the problem, I am just trying to give a solution.
> 
> well, I know that it doesn't make much sense. This setup was made to
> "balance" the traffic coming in to the machine. I know that there's
> not much  difference between one NIC running at, say 400 Mbps, or
> two NICs running at 200 Mbps each which will also be 400 Mbps, because
> the machine can't handle more traffic (data (backups) is received via
> network from other machines and written to disks)...but as I've already
> written, this wasn't my decision...
<snip>
Unfortunately, I don't have the time right now to think this challenging
issue all the way through but I'll share my first thoughts.  As they are
first thoughts, they may be completely worthless :-)

Like Alexander, I would think iproute2 could be your friend.  I am under
the impression that some of its features are explicitly to load balance
across multiple NICs on the same interface but I don't recall what gave
me that impression.

You may find some other options outside of routing.  If you have
specific services, you may be able to bind those services to a
particular address.  For lack of a better example, let's assume we bind
Apache to 1.2.3.4 and an Asterisk IP PBX to 1.2.3.5.  You could set up
two different DNS entries for the two sets of services:
web.mycompany.com is 1.2.3.4
pbx.mycompany.com is 1.2.3.5

I'm not sure if that will confuse anything.  Just some raw thoughts.  I
hope they help - John


-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net 



  parent reply	other threads:[~2004-11-05 15:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 12:38 2 NICs on same subnet Sven Schuster
2004-11-05 12:41 ` Marc Haber
2004-11-05 12:54   ` Sven Schuster
2004-11-05 13:04     ` Marc Haber
2004-11-05 14:22       ` Sven Schuster
2004-11-05 14:52         ` Lumberjack
2004-11-05 15:25         ` Jason Opperisano
2004-11-05 15:32         ` John A. Sullivan III [this message]
2004-11-05 14:12 ` Jason Opperisano
2004-11-05 14:47 ` Aleksandar Milivojevic
2004-11-05 14:51   ` Aleksandar Milivojevic
2004-11-05 17:07   ` a.ledvinka
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 13:00 Scott Knake
2004-11-05 13:21 ` Sven Schuster
2004-11-05 18:45 Daniel Chemko
2004-11-05 19:16 ` Sven Schuster
2004-11-05 23:37   ` Jorge Nerín
2004-11-06  0:05     ` George Alexandru Dragoi

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=1099668758.4891.114.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=schuster.sven@gmx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox