From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: Documentation (was Re: randomly changing IPs from different subnets (Google Mail))
Date: Wed, 23 Jun 2010 10:13:45 -0500 [thread overview]
Message-ID: <20100623151345.GT19868@cardinal> (raw)
In-Reply-To: <4C221BF0.40609@gmail.com>
On Wed, Jun 23, 2010 at 05:36:32PM +0300, Lars Nooden wrote:
> /dev/rob0 wrote:
>
> > http://www.netfilter.org/news.html :
> >
> > "2004-Jun-15
> > New iptables 1.2.10 release ..."
> >
> > That was SIX YEARS ago.
>
> Yes and it has worked very well for SIX YEARS on those particular
> servers.
FWIW I have a Slackware 10.0 server with iptables 1.2.10, which will
be six years old in October. Nothing wrong with not upgrading if a
server is working fine.
The point is: I don't assume that's up-to-date. Two years is a long
time in Linux terms, and we have had three such long times since A.D.
2004.
> What can be done about the old web tutorials and howtos? Many have
> not been touched in years, even if only to refresh the date stamp
Stamp a big red warning label on the whole WWW, stating that content
is provided as-is and with no guarantees. :)
> and say things are still valid or to post a warning for staleness.
> e.g.:
>
> http://www.netfilter.org/documentation/HOWTO//networking-concepts-HOWTO.html
>
> If I had to choose one to start with, it might be the Oskar
> Andreasson tutorial:
>
> http://www.frozentux.net/documents/iptables-tutorial/
I think Oskar's is still the definitive work, but indeed, it shows
its age. If I could get a grant, I would be happy to start work on
updating Oskar's tutorial and Rusty's Unreliable Guides.
Such grants are more likely to be offered to actual Netfilter
developers, of course. They're more deserving than I am. But I'm
stuck with bills and expenses, so I have to find something which
pays. When someone with the time to spare comes along and wants to
fill the need, it will be done.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
next prev parent reply other threads:[~2010-06-23 15:13 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
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 [this message]
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=20100623151345.GT19868@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).