From: Sander Sneekes <sander@dmdsecure.com>
To: "Daniel F. Chief Security Engineer -" <danielf@supportteam.net>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: load balancing
Date: 04 Feb 2003 16:35:11 +0100 [thread overview]
Message-ID: <1044372911.22297.69.camel@sander> (raw)
In-Reply-To: <200302031030.53569.danielf@supportteam.net>
[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]
yepz thank daniel got the stuff working
also will the a deeper look to iproute
thx sander
On Mon, 2003-02-03 at 17:30, Daniel F. Chief Security Engineer - wrote:
> Im going to be working on one of these later this year it's my understanding
> that you would want to use the nth patch and the state table and SNAT to
> accoplish this.
>
> From the nth patch.
> ------------------------
> 2) Unique rule for every packet. This is an easy and quick
> method to produce load-balancing for both inbound and outbound.
> example:
> iptables -t nat -A POSTROUTING -o eth0 -m nth --counter 7
> --every 3 --packet 0 -j SNAT --to-source 10.0.0.5
> iptables -t nat -A POSTROUTING -o eth0 -m nth --counter 7
> --every 3 --packet 1 -j SNAT --to-source 10.0.0.6
> iptables -t nat -A POSTROUTING -o eth0 -m nth --counter 7
> --every 3 --packet 2 -j SNAT --to-source 10.0.0.7
> This example evenly splits connections between the three SNAT
> addresses.
>
> By using the mangle table and iproute2, you can setup complex
> load-balanced routing.
> ------------------------
>
> Here's a site with good infos on the patches available.
> http://www.netfilter.org/documentation/HOWTO//netfilter-extensions-HOWTO.html
>
> Hope this helps.
>
> On Monday 03 February 2003 08:35, Sander Sneekes wrote:
> > currently i'm using this line
> >
> > iptable -t nat -A PREROUTING -d X.X.X.X -p tcp --dport http -j DNAT
> > --to-dest 192.168.0.100-192.168.0.111
> >
> > this this the job but the if i use the same client it always uses 100
> > for ex.
> >
> > but we need to do some preformance test with 3 client's so everytime a
> > client
> > does a reqeust to the http server i want to get it for a different
> > server.
> >
> > anybody ?
> >
> > thanks
> > Sander
> >
> > On Mon, 2003-02-03 at 14:49, Sander Sneekes wrote:
> > > Hi all,
> > >
> > > I need to load balance between 2 webserver
> > > what is the most fastest way of doing this?
> > > With iptables? if yes wich line's do i need to use
> > > i have a RH 7.2 with iptables running already doing
> > > al network traffic
> > >
> > > cheers
> > > Sander
[-- Attachment #2: Type: text/html, Size: 2666 bytes --]
next prev parent reply other threads:[~2003-02-04 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 13:49 load balancing Sander Sneekes
2003-02-03 14:35 ` Sander Sneekes
2003-02-03 16:30 ` Daniel F. Chief Security Engineer -
2003-02-04 15:35 ` Sander Sneekes [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 10:59 Load Balancing Allan de Borde
2003-04-02 11:16 Allan de Borde
2003-04-02 16:43 ` Matthew G. Marsh
2003-04-02 15:24 Carlos Ble
2003-04-03 7:40 Allan de Borde
2003-07-12 19:05 LOAD BALANCING Javier Govea
2005-04-03 19:17 Load balancing szpak
2005-04-03 20:49 ` Pablo Neira
2005-04-04 3:23 ` Grant Taylor
2005-04-04 9:46 Visham Ramsurrun
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=1044372911.22297.69.camel@sander \
--to=sander@dmdsecure.com \
--cc=danielf@supportteam.net \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox