From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Elise Lennion <elise.lennion@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft v3] datatype: Display pre-defined inet_service values in host byte order
Date: Sat, 10 Dec 2016 14:16:40 +0100 [thread overview]
Message-ID: <20161210131640.GA30182@salvia> (raw)
In-Reply-To: <20161210003513.GA30388@lennorien.com>
On Fri, Dec 09, 2016 at 10:35:13PM -0200, Elise Lennion wrote:
> nft describe displays, to the user, which values are available for a selector,
> then the values should be in host byte order.
>
> Variable size was replaced by len to better match the common pattern.
Applied, thanks Elise.
BTW, I have moved switch_byteorder() to datatype.c, I remember I
suggested you to place it under gmputil.c but given this doesn't take
any mpz_t parameter, let's keep it where we use it and remember this
is there.
Anyway, another issue that would be good to revisit:
# nft describe tcp dport
payload expression, datatype inet_service (internet network service)
(basetype integer), 16 bits
pre-defined symbolic constants:
tcpmux 0x0001
echo 0x0007
discard 0x0009
...
The convention is to represent ports in base 10, not as hex. So if you
can follow up with a patch to solve this I'd appreciate it.
Probably this is a new field we can place in struct symbol_table.
Thanks.
prev parent reply other threads:[~2016-12-10 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 0:35 [PATCH nft v3] datatype: Display pre-defined inet_service values in host byte order Elise Lennion
2016-12-10 13:16 ` 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=20161210131640.GA30182@salvia \
--to=pablo@netfilter.org \
--cc=elise.lennion@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).