[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpxKHGa6DpV-9n8La7wh6r7MbEZpzGTWOO1AhmhWv072b4LAg@mail.gmail.com>
Date: Wed, 10 Jul 2019 13:55:25 +0700
From: Naruto Nguyen <narutonguyen2018@...il.com>
To: Florian Westphal <fw@...len.de>
Cc: netfilter-devel@...r.kernel.org, netdev@...r.kernel.org,
netfilter@...r.kernel.org
Subject: Re: Question about nf_conntrack_proto for IPsec
Hi Florian,
Thanks a lot for your reply.
Could you please elaborate more on how generic tracker tracks ESP connection?
Brs,
Bao
On Wed, 26 Jun 2019 at 18:13, Florian Westphal <fw@...len.de> wrote:
>
> Naruto Nguyen <narutonguyen2018@...il.com> wrote:
> > In linux/latest/source/net/netfilter/ folder, I only see we have
> > nf_conntrack_proto_tcp.c, nf_conntrack_proto_udp.c and some other
> > conntrack implementations for other protocols but I do not see
> > nf_conntrack_proto for IPsec, so does it mean connection tracking
> > cannot track ESP or AH protocol as a connection. I mean when I use
> > "conntrack -L" command, I will not see ESP or AH connection is saved
> > in conntrack list. Could you please help me to understand if conntrack
> > supports that and any reasons if it does not support?
>
> ESP/AH etc. use the generic tracker, i.e. only one ESP connection
> is tracked between each endpoint.
Powered by blists - more mailing lists