All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] flow classification
Date: Mon, 10 Nov 2003 23:59:18 +0000	[thread overview]
Message-ID: <marc-lartc-106850901724536@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106848100920399@msgid-missing>

> i have 2 links to the ISP of 128kbit each, and i want to balance the
> trafic between them, but not staticly (local ip1-5 throw isp1, and the
> rest to isp2). I though at a ingress clasification, then routing by the
> mark, and at the exit nat (yes i must do nat :(((, but the clasification
> must be flow based, and i dont know how to do it.

If certain IPs are always going through the same link, then you don't really want 
load balancing at all.
Don't you just want routing rules that say local ip1-5 always go through one gateway 
(isp1), and the default route is isp2 for everyone else?

Or did I misunderstand?


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer  email:     damion@snapgear.com
SnapGear ---                           ph:         +61 7 3435 2809
  | Custom Embedded Solutions          fax:         +61 7 3891 3630
  | and Security Appliances            web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ---  Free Embedded Linux Distro at   http://www.snapgear.org  ---

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

  reply	other threads:[~2003-11-10 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 15:54 [LARTC] flow classification Ciprian Niculescu
2003-11-10 23:59 ` Damion de Soto [this message]
2003-11-11 11:09 ` Ciprian Niculescu

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-106850901724536@msgid-missing \
    --to=damion@snapgear.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.