From: Herve Eychenne <rv@wallfire.org>
To: Netfilter Development <netfilter-devel@lists.netfilter.org>
Subject: Re: modified iptables manpage
Date: Tue, 17 Aug 2004 22:56:27 +0200 [thread overview]
Message-ID: <20040817205627.GD23109@eychenne.org> (raw)
In-Reply-To: <20040708181030.GB5877@eychenne.org>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
On Thu, Jul 08, 2004 at 08:10:30PM +0200, Herve Eychenne wrote:
> On Mon, Jul 05, 2004 at 01:57:40PM +0200, Hervé Eychenne wrote:
> Here it is:
> - fixed weird characters handling in interface name
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102771&archive=yes
> - fixed typo in manpage (the fix was wrong in Debian...)
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197619&archive=yes
> - added the default logging level (target LOG) to the manpage
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246037
> There are still some patches in the iptables Debian package, that the
> coreteam may want to apply... it's up to you.
> Sebastien Chaumontet reported that the ability to change only port in
> DNAT was not documented in the manpage. The attached patch fixes that
> as well.
> The patch also reflects the status of the new (ok, this one is pending
> for a few months) emeritus members status.
> Over time, a few people told me that they first had looked for a
> netfilter man page, before finding the iptables one... and I agree
> there should definitely be a small man page about netfilter,
> containing only a little information about the very basic concepts
> and the kernel part, just to clarify things.
> Of course, it is not intended to grow too much, as it would overlap
> with the howto, which is clearly not its goal.
> So I joined a netfilter.7 manpage, as it was pending (too) in
> my tree for a long time. Feel free to include it (and correct by bad
> english) if you find it useful.
> Note: the patch is against current CVS.
Apparently this mail/patch was lost/ignored... may I dare to ask why?
But you won't discourage me ;-), so I send another patch on top of
that.
Eric Raymond sent me an email, as the iptables man page did not pass his
groff validator. He was right, so here is the patch, which also fixes
a typo (address only takes one d in french, so this is a quite common
mistake down here, I guess...)
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
[-- Attachment #2: iptables.patch2 --]
[-- Type: text/plain, Size: 1141 bytes --]
diff -ruN iptables.old/extensions/libipt_DNAT.man iptables/extensions/libipt_DNAT.man
--- iptables.old/extensions/libipt_DNAT.man 2004-07-08 19:29:46.000000000 +0200
+++ iptables/extensions/libipt_DNAT.man 2004-07-19 21:20:48.000000000 +0200
@@ -27,4 +27,5 @@
You can add several --to-destination options. If you specify more
than one destination address, either via an address range or multiple
--to-destination options, a simple round-robin (one after another in
-cycle) load balancing takes place between these adresses.
+cycle) load balancing takes place between these addresses.
+.RE
diff -ruN iptables.old/extensions/libipt_SNAT.man iptables/extensions/libipt_SNAT.man
--- iptables.old/extensions/libipt_SNAT.man 2004-01-22 16:04:24.000000000 +0100
+++ iptables/extensions/libipt_SNAT.man 2004-07-19 21:21:16.000000000 +0200
@@ -23,4 +23,5 @@
You can add several --to-source options. If you specify more
than one source address, either via an address range or multiple
--to-source options, a simple round-robin (one after another in
-cycle) takes place between these adresses.
+cycle) takes place between these addresses.
+.RE
prev parent reply other threads:[~2004-08-17 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 11:57 modified iptables manpage Hervé Eychenne
2004-07-08 18:10 ` Herve Eychenne
2004-08-17 20:56 ` Herve Eychenne [this message]
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=20040817205627.GD23109@eychenne.org \
--to=rv@wallfire.org \
--cc=netfilter-devel@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 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.