From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Quentin Armitage <quentin@armitage.org.uk>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: nftables: fix documentation for dup statement
Date: Thu, 27 Aug 2020 19:55:17 +0200 [thread overview]
Message-ID: <20200827175517.GA24746@salvia> (raw)
In-Reply-To: <f9bc9e191b03728fe233ca7a75fdc40ede0fde8e.camel@armitage.org.uk>
Hi Quentin,
Thanks for your patch:
On Thu, Aug 27, 2020 at 04:42:00PM +0100, Quentin Armitage wrote:
>
> The dup statement requires an address, and the device is optional,
> not the other way round.
table netdev x {
chain y {
type filter hook ingress device "eth0" priority filter; policy accept;
ip protocol udp dup to "eth1"
}
}
I think probably it should be good to clarify that:
- dup to 'device'
- fwd to 'device'
only work from the netdev family.
Thanks.
> Signed-off-by: Quentin Armitage <quentin@armitage.org.uk>
> ---
> doc/statements.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/statements.txt b/doc/statements.txt
> index 9155f286..835db087 100644
> --- a/doc/statements.txt
> +++ b/doc/statements.txt
> @@ -648,7 +648,7 @@ The dup statement is used to duplicate a packet and send the
> copy to a different
> destination.
>
> [verse]
> -*dup to* 'device'
> +*dup to* 'address'
> *dup to* 'address' *device* 'device'
>
> .Dup statement values
> --
> 2.25.4
>
>
prev parent reply other threads:[~2020-08-27 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 15:42 [PATCH] netfilter: nftables: fix documentation for dup statement Quentin Armitage
2020-08-27 17:02 ` Phil Sutter
2020-08-27 17:40 ` Florian Westphal
2020-08-27 18:59 ` Quentin Armitage
2020-08-31 16:49 ` Phil Sutter
2020-09-03 8:15 ` Quentin Armitage
2020-08-27 17:55 ` Pablo Neira Ayuso [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=20200827175517.GA24746@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=quentin@armitage.org.uk \
/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.