From: "Dennis O. Aliev" <doa@einsteinindustries.com>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Multiple Source IP Addresses
Date: Fri, 11 Mar 2005 12:37:31 -0800 [thread overview]
Message-ID: <20050311123731.223acf05.doa@einsteinindustries.com> (raw)
In-Reply-To: <1110570591.4767.57.camel@hubcap.ljm.dom>
Jason,
This is a great solution, but it has 1 limitation. There would be no way for webserver to track how many requests went through each external IP. Would you have any further suggestions?
Thanks a lot.
Dennis O. Aliev
On Fri, 11 Mar 2005 14:49:51 -0500
Jason Opperisano <opie@817west.com> wrote:
> On Fri, 2005-03-11 at 14:40, Dennis O. Aliev wrote:
> > Baake,
> >
> > Thank you for reply.
> >
> > What you suggesting will take care of routing incomming packets (from internet) to web server. In my scenario, I have a bot that parses sites and so the packets are coming from webserver to internet and source addresses must be different to load balance between internet connections.
>
> use multiple "--to-source" options in your SNAT rule:
>
> iptables -t nat -A POSTROUTING -o $EXT_IF -s $WEB_SRV_IP \
> -j SNAT --to-source $EXTIP1 --to-source $EXTIP2 --to-source $EXTIP3
>
> outbound connections will round-robin between the source addresses.
>
> -j
>
> --
> "Alright brain, you don't like me and I don't like you. But let's just
> get through this and then I can get back to killing you with beer."
> --The Simpsons
>
next prev parent reply other threads:[~2005-03-11 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 8:21 Multiple Source IP Addresses Baake, Matthias
2005-03-11 19:40 ` Dennis O. Aliev
2005-03-11 19:49 ` Jason Opperisano
2005-03-11 20:37 ` Dennis O. Aliev [this message]
2005-03-11 20:48 ` Dennis O. Aliev
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 3:50 Dennis O. Aliev
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=20050311123731.223acf05.doa@einsteinindustries.com \
--to=doa@einsteinindustries.com \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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.