netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: randomly changing IPs from different subnets (Google Mail)
Date: Wed, 23 Jun 2010 09:12:13 -0500	[thread overview]
Message-ID: <20100623141213.GR19868@cardinal> (raw)
In-Reply-To: <4C22105A.70006@gmail.com>

On Wed, Jun 23, 2010 at 04:47:06PM +0300, Lars Nooden wrote:
> Am 23.06.2010 um 14:54 schrieb Jan Engelhardt:
>> Do not start grepping in iptables -L.
>
> There is also building iptables rules with a script and re-run
> that as an option.

Scripts are not recommended because of the possibility of race 
conditions. iptables-restore(8) changes rulesets atomically.

>> That is what iptables -S and iptables-save are much better suited 
>> for.
>
> Perhaps the manual pages are out of date then.  There appears to be 
> no mention of the option -S in the manual page for iptables v1.2.10 
> or on this web page:
>
> 	http://linux.die.net/man/8/iptables
>
> % iptables -S
> iptables v1.2.10: Unknown arg `-S'
> Try `iptables -h' or 'iptables --help' for more information.

http://www.netfilter.org/news.html :

"2004-Jun-15
	New iptables 1.2.10 release ..."

That was SIX YEARS ago.

> Where are you finding -S ?

What is out of date is your version of iptables and that Web page. 
Manuals for recent releases of iptables are up-to-date.
-- 
    Offlist mail to this address is discarded unless
    "/dev/rob0" or "not-spam" is in Subject: header

  parent reply	other threads:[~2010-06-23 14:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 18:16 randomly changing IPs from different subnets (Google Mail) Florian Effenberger
2010-06-22 18:19 ` Jan Engelhardt
2010-06-22 18:30   ` Florian Effenberger
2010-06-22 19:16     ` Lars Nooden
2010-06-23  8:53       ` Florian Effenberger
2010-06-23  9:33         ` Mart Frauenlob
2010-06-23 16:46           ` Florian Effenberger
2010-06-23 11:52         ` Lars Nooden
2010-06-23 11:54           ` Jan Engelhardt
2010-06-23 13:47             ` Lars Nooden
2010-06-23 13:52               ` John Haxby
2010-06-23 14:12               ` /dev/rob0 [this message]
2010-06-23 14:36                 ` Documentation (was Re: randomly changing IPs from different subnets (Google Mail)) Lars Nooden
2010-06-23 15:13                   ` /dev/rob0
2010-06-23 16:00                     ` Jan Engelhardt
2010-06-23 16:15                       ` Lars Nooden
2010-06-23 16:36                         ` Jan Engelhardt
2010-06-23 18:34                           ` Grant Taylor
2010-06-23 18:41                             ` Jan Engelhardt
2010-06-23 18:53                               ` Grant Taylor
2010-06-24  6:17                     ` Andrew Beverley
2010-06-24 16:45                       ` Grant Taylor
2010-06-23 16:44           ` randomly changing IPs from different subnets (Google Mail) Florian Effenberger
2010-06-23 18:36           ` Grant Taylor
2010-06-22 19:18     ` Jan Engelhardt
2010-06-22 18:55 ` Jeff Largent
2010-06-23  1:09   ` /dev/rob0
2010-06-23  1:22     ` Mike Lay

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=20100623141213.GR19868@cardinal \
    --to=rob0@gmx.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).