All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: documentation bug: missing nat targets in man
Date: Wed, 10 Apr 2013 14:53:52 +0200	[thread overview]
Message-ID: <516560E0.6000605@chello.at> (raw)
In-Reply-To: <20130410112623.GB21728@macbook.localnet>

On 10.04.2013 13:26, Patrick McHardy wrote:
> On Tue, Apr 09, 2013 at 01:40:24PM +0200, Mart Frauenlob wrote:
>> On 09.04.2013 11:54, Patrick McHardy wrote:
>>> On Tue, Apr 09, 2013 at 11:47:42AM +0200, Mart Frauenlob wrote:
>>>> Hello,
>>>>
>>>> I noticed there's quite new DNAT, SNAT, NETMAP support for
>>>> ip6tables, but that information is missing in the man page.
>>>> Anything else needed than just copying the according ipv4 *.man files?
>>>> If so, want me do prepare a patch?
>>>
>>> I guess you can rename the ipv4 specific man files to xt_... and
>>> update them accordingly, the modules should behave similar to their
>>> IPv4 counterparts.
>>>
>>
>> Ok, here it is.
>> I slightly modified the text in regards to sentence structure.
>> Removed the references to older kernels, as this does not apply to
>> the new ipv6 version.
>> Added the list of valid protocols, which again - for me leaves the
>> question about -p icmp open (re other mail).

[...]
>> ---
>>   extensions/libip6t_DNAT.man   |   30 ++++++++++++++++++++++++++++++
>>   extensions/libip6t_NETMAP.man |    9 +++++++++
>>   extensions/libip6t_SNAT.man   |   28 ++++++++++++++++++++++++++++
>>   3 files changed, 67 insertions(+), 0 deletions(-)
>>   create mode 100644 extensions/libip6t_DNAT.man
>>   create mode 100644 extensions/libip6t_NETMAP.man
>>   create mode 100644 extensions/libip6t_SNAT.man
>
> Well, my suggestion was to add one manpage which covers both the IPv4
> and IPv6 targets since they're pretty much identical. I think just
> adding a libxt_DNAT.man etc. should work.

I've not yet tried to figure out where and what code is responsible for 
assembling all the *.man files together, but from what I see as the 
result and from what is there, like the LOG or MASQUERADE target are 
split up that way, actually producing redundant sections. Thats why I 
thought thats the way to go. Will try the libxt_*.man way...


As there's redundant stuff, I can also prepare patches to join that 
together. Wanted?

What about the -p icmp part?

Best regards

Mart


  reply	other threads:[~2013-04-10 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  9:47 documentation bug: missing nat targets in man Mart Frauenlob
2013-04-09  9:54 ` Patrick McHardy
2013-04-09 11:40   ` Mart Frauenlob
2013-04-10 11:26     ` Patrick McHardy
2013-04-10 12:53       ` Mart Frauenlob [this message]
2013-04-10 13:20         ` Patrick McHardy

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=516560E0.6000605@chello.at \
    --to=mart.frauenlob@chello.at \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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.