From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: l3num is u_int16_t Date: Mon, 19 Dec 2005 19:13:29 +0100 Message-ID: <43A6F849.6070602@eurodev.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Netfilter Development Mailinglist Return-path: To: Yasuyuki Kozakai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Hi Yasuyuki, /* The manipulable part of the tuple. */ struct nf_conntrack_man { union nf_conntrack_man_l3proto u3; union nf_conntrack_man_proto u; /* Layer 3 protocol */ u_int16_t l3num; }; struct nfgenmsg { u_int8_t nfgen_family; /* AF_xxx */ u_int8_t version; /* nfnetlink version */ u_int16_t res_id; /* resource id */ } __attribute__ ((packed)); There's some inconsistency here: why l3num is u_int16_t but nfgen_family in u_int8_t? AFAIK, both designates the same thing, the layer 3 protocol number. -- Pablo