From: "Timothy Hayes" <morphieus@earthlink.net>
To: 'Mail List - Netfilter' <netfilter@vger.kernel.org>
Subject: snat range not cycling
Date: Tue, 3 Aug 2010 15:06:02 -0700 [thread overview]
Message-ID: <003901cb3358$1346b250$39d416f0$@net> (raw)
In-Reply-To: <x6sk2vo9eq@gzp>
Hi guys I've got a iptables firewall setup and a request came in to not just
snat an address but to make each subsequent connection go to a range of
address.
The firewall doesn't normally handle traffic from this particular
application so I've setup a squid proxy and the app is connecting to the
proxy.
I added the range of addresses with ip addr add x.x.x.# dev eth0
and setup a snat rule:
iptables -A POSTROUTING -o eth0 -p tcp --dport 80 -j SNAT --to-source
xx.xx.xx.131-xx.xx.xx.250
translation works fine, but I never seem to get an alternate ip from the
range.
If anyone knows what I need to do to make it so that the source addresses
cycle it would be much appreciated.
next prev parent reply other threads:[~2010-08-03 22:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:17 [ANNOUNCE]: Release of iptables-1.4.9 Patrick McHardy
2010-08-03 16:34 ` Gabor Z. Papp
2010-08-03 16:34 ` Gabor Z. Papp
2010-08-03 17:05 ` Patrick McHardy
2010-08-03 17:16 ` Gabor Z. Papp
2010-08-03 17:16 ` Gabor Z. Papp
2010-08-03 17:25 ` Gabor Z. Papp
2010-08-03 17:25 ` Gabor Z. Papp
2010-08-03 18:04 ` Jan Engelhardt
2010-08-03 18:09 ` Gabor Z. Papp
2010-08-03 18:09 ` Gabor Z. Papp
2010-08-03 18:34 ` Jan Engelhardt
2010-08-04 17:23 ` Gabor Z. Papp
2010-08-04 17:23 ` Gabor Z. Papp
2010-08-03 22:06 ` Timothy Hayes [this message]
2010-08-03 22:09 ` snat range not cycling Jan Engelhardt
2010-08-04 5:43 ` "Oleg A. Arkhangelsky"
2010-08-04 6:42 ` Timothy Hayes
2010-08-04 6:52 ` "Oleg A. Arkhangelsky"
2010-08-04 8:00 ` Jan Engelhardt
2010-08-04 16:16 ` [ANNOUNCE]: Release of iptables-1.4.9 Patrick McHardy
2010-08-04 16:32 ` Jan Engelhardt
2010-08-06 13:15 ` Patrick McHardy
2010-08-03 17:29 ` Michele Petrazzo - Unipex
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='003901cb3358$1346b250$39d416f0$@net' \
--to=morphieus@earthlink.net \
--cc=netfilter@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.