From: "mpboden" <mpboden@surfcity.net>
To: netfilter@lists.netfilter.org
Subject: RE: using iptables for poor-man's load balancing?
Date: Wed, 19 Feb 2003 19:00:27 -0800 [thread overview]
Message-ID: <001b01c2d88c$385830c0$483918ac@C1006818> (raw)
In-Reply-To: 20030219232644.14732.18331.Mailman@kashyyyk
i was recently reading the "Iptables Tutorial 1.1.16" by Oskar Andreasson,
and i'm getting the impression that your rules might be written incorrectly.
of course, i could be wrong, but if you check the following link,
http://iptables-tutorial.frozentux.net/chunkyhtml/targets.html, he
specifically talks about load balancing. in essence, he specifies a range of
ip addresses that the packets would randomly go to, and this is specified in
only one "--to-destination" instead of two as you have it written. the
following rule would send the packets randomly to any of the servers with
ip's from 192.168.1.1. through 192.168.1.12.
iptables -t nat -A PREROUTING -p tcp -d 1.2.3.4 --dport 80 -j
DNAT --to-destination 192.168.1.1-192.168.1.12
so perhaps a comma would work in your case if you specifically need to have
the ip's as you have them. i've never tried this, but it seems to make sense
to me.
iptables -t nat -A PREROUTING -p tcp -d 1.2.3.4 --dport 80 -j
DNAT --to-destination 192.168.1.1,192.168.1.12
furthermore, he mentions adding two more specific rules in the nat table to
allow hosts on the LAN as well as the firewall computer itself to access the
servers properly. please check those out.
mike
> Message: 7
> From: "Ian Douglas" <ian@icreditvision.com>
> To: <netfilter@lists.netfilter.org>
> Subject: RE: using iptables for poor-man's load balancing?
> Date: Wed, 19 Feb 2003 15:17:48 -0800
>
> > Say for argument's sake that our public IP is 1.2.3.4 and our
> > internal LAN machines are:
> > 192.168.1.1
> > 192.168.1.12
>
> (cut two of them out since they're not actually ready to run yet)
>
> > Just curious if the following rules would work to round-robin the
connections:
> >
> > /sbin/iptables -t nat -A PREROUTING -p udp -d 1.2.3.4 --dport 80 -j
DNAT \
> > --to-destination 192.168.1.1:80 \
> > --to-destination 192.168.1.12:80
> > /sbin/iptables -t nat -A PREROUTING -p udp -d 1.2.3.4 --dport 433 -j
DNAT \
> > --to-destination 192.168.1.1:80 \
> > --to-destination 192.168.1.12:80
>
> I tested this last night and it didn't work - every request went to 1.1
>
> Should I be using "--to 192.168.1.1:80" instead of "--to-destination
> 192.168.1.1:80" ? I've seen documentation show the use of --to and a
working
> script for port forwarding that uses --to-destination
>
> As a followup:
>
> # uname -a
> Linux icv.com 2.4.18-18.7.x #1 Wed Nov 13 20:29:30 EST 2002 i686 unknown
>
> # rpm -qa | grep iptables
> iptables-1.2.5-3
> iptables-ipv6-1.2.5-3
>
> # iptables -V
> iptables v1.2.5
>
> Andrej (Tink) suggested I write the list again and ask what version of
iptables
> introduced 'multiple targets' for port forwarding.
>
next parent reply other threads:[~2003-02-20 3:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030219232644.14732.18331.Mailman@kashyyyk>
2003-02-20 3:00 ` mpboden [this message]
2003-02-20 3:39 ` using iptables for poor-man's load balancing? SBlaze
2003-02-18 22:10 Andrej Ricnik
2003-02-19 18:47 ` Ian Douglas
-- strict thread matches above, loose matches on Subject: below --
2003-02-18 21:53 Ian Douglas
2003-02-18 22:02 ` Ian Douglas
2003-02-19 23:17 ` Ian Douglas
2003-02-20 0:12 ` Joel Newkirk
2003-02-20 0:30 ` Joel Newkirk
2003-02-20 0:55 ` Ian Douglas
2003-02-20 4:24 ` Joel Newkirk
2003-02-21 8:48 ` Fabrice MARIE
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='001b01c2d88c$385830c0$483918ac@C1006818' \
--to=mpboden@surfcity.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