From: Florian Westphal <fw@strlen.de>
To: Cristian Constantin <const.crist@googlemail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: integers byte order in netlink/NETLINK_NETFILTER messages
Date: Fri, 17 Sep 2021 11:44:28 +0200 [thread overview]
Message-ID: <20210917094428.GC15906@breakpoint.cc> (raw)
In-Reply-To: <CANCV4NPXskt-r4RNfQJeacoOAmKFjuV6CSKtqEe=gyCbpiZMaQ@mail.gmail.com>
Cristian Constantin <const.crist@googlemail.com> wrote:
> in general, how are the integers encoded in the attributes of the
> NETLINK_NETFILTER messages: host byte order or network byte order?
Network byte order.
> the same byte order supposed to be used by both user space tools and
> the kernel?
Yes, all need to use network byte order.
> in particular, how is the chain policy attribute encoded by the kernel
> when it sends an reply to a NFT_MSG_GETCHAIN request?
Network byte order.
next prev parent reply other threads:[~2021-09-17 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 8:45 integers byte order in netlink/NETLINK_NETFILTER messages Cristian Constantin
2021-09-17 9:44 ` Florian Westphal [this message]
2021-09-30 14:03 ` Pablo Neira Ayuso
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=20210917094428.GC15906@breakpoint.cc \
--to=fw@strlen.de \
--cc=const.crist@googlemail.com \
--cc=netfilter@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