Marcelo Ricardo Leitner <mleit...@redhat.com> wrote: > > us too: > > enum ip_conntrack_info { > IP_CT_ESTABLISHED, = 0 > IP_CT_RELATED, = 1 > IP_CT_NEW, = 2 > IP_CT_IS_REPLY, = 3 <-- > IP_CT_ESTABLISHED_REPLY = IP_CT_ESTABLISHED + IP_CT_IS_REPLY, > 0 + 3 = 3 <--
Don't worry, there is no IP_CT_ESTABLISHED_REPLY state, just pretend you did not see it :-) As for UAPI, I suggest to check net/netfilter/nft_ct.c which already exposes established/new/invalid and so on.