All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: documentation bug: missing nat targets in man
Date: Tue, 9 Apr 2013 11:54:48 +0200	[thread overview]
Message-ID: <20130409095448.GD26170@macbook.localnet> (raw)
In-Reply-To: <5163E3BE.3040609@chello.at>

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.

  reply	other threads:[~2013-04-09  9: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 [this message]
2013-04-09 11:40   ` Mart Frauenlob
2013-04-10 11:26     ` Patrick McHardy
2013-04-10 12:53       ` Mart Frauenlob
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=20130409095448.GD26170@macbook.localnet \
    --to=kaber@trash.net \
    --cc=mart.frauenlob@chello.at \
    --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.