From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dennis O. Aliev" Subject: Re: Multiple Source IP Addresses Date: Fri, 11 Mar 2005 12:37:31 -0800 Message-ID: <20050311123731.223acf05.doa@einsteinindustries.com> References: <201E6F5AC48C274996A5AD8304FAEF869A04@p001ex03.porta.local> <20050311114010.7d7207ec.daliev@etecom.com> <1110570591.4767.57.camel@hubcap.ljm.dom> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit In-Reply-To: <1110570591.4767.57.camel@hubcap.ljm.dom> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" To: Jason Opperisano Cc: netfilter@lists.netfilter.org 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 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 >