I am marking this as an RFC and including this cover letter, because I'm not absolutely 100% sure that the current code is incorrect. (It obviously works, or this would have come up before.) AFAICT, the res_id of struct nfgenmsg is supposed to be in network byte order, and that isn't happening on little endian systems. nftnl_batch_begin() and nftnl_batch_end() both pass NFNL_SUBSYS_NFTABLES (10) to __nftnl_nlmsg_build_hdr(), but without a call to htons(), the message contains 2560 (when interpretted in network byte order). Ian Pilcher (1): libnftnl: Fix res_id byte order src/common.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) base-commit: 461f36979f4ed2b6cc95f06cf5f9c3c84bdf9e70 -- 2.37.3
