From: Nic <nferrier@tapsellferrier.co.uk>
To: djTremors@newjackswing.dyndns.org
Cc: netfilter@lists.netfilter.org
Subject: about the iptables tutorial and the state of documentation
Date: 13 Jul 2003 01:29:57 +0100 [thread overview]
Message-ID: <87znjjp8u2.fsf@tapsellferrier.co.uk> (raw)
After much searching around for info about the state of netfilter I
found your reference to the tutorial.
Thanks for mailing that to the list, without it I would never have
found out exactly what the situation is.
This is due to the awful state of the netfilter documentation. The
kernel documentation says that netfilter modules are no longer
included (it certainly doesn't seem possible to turn them on with
menuconfig) but the current netfilter documentation makes no mention
of that at all.
Maybe I've got the wrong end of the stick about all of this... but I'm
not an inexperienced linux admin and I was mighty confused. I dead to
think what someone coming from solaris of (horrors!) nt would think.
--
Nic Ferrier
http://www.tapsellferrier.co.uk
next reply other threads:[~2003-07-13 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 0:29 Nic [this message]
2003-07-15 16:09 ` about the iptables tutorial and the state of documentation Harald Welte
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=87znjjp8u2.fsf@tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=djTremors@newjackswing.dyndns.org \
--cc=netfilter@lists.netfilter.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