Re: [PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-15 Thread Eric Leblond
Hi, On Mon, 2017-05-15 at 19:55 +0200, Pablo Neira Ayuso wrote: > On Mon, May 15, 2017 at 07:49:18PM +0200, Eric Leblond wrote: > >    Hello, > >    Le 15 mai 2017 6:52 PM, Pablo Neira Ayuso > > a > >    écrit : > > > >  On Thu, May 11, 2017 at 06:56:38PM +0200, Eric

Re: [PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-15 Thread Pablo Neira Ayuso
On Mon, May 15, 2017 at 07:49:18PM +0200, Eric Leblond wrote: >Hello, >Le 15 mai 2017 6:52 PM, Pablo Neira Ayuso a >écrit : > > On Thu, May 11, 2017 at 06:56:38PM +0200, Eric Leblond wrote: > > This patch fixes the creation of connection tracking entry

Re: [PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-15 Thread Pablo Neira Ayuso
On Thu, May 11, 2017 at 06:56:38PM +0200, Eric Leblond wrote: > This patch fixes the creation of connection tracking entry from > netlink when synproxy is used. It was missing the addition of > the synproxy extension. > > This was causing kernel crashes when a conntrack entry created by >

[PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-11 Thread Eric Leblond
This patch fixes the creation of connection tracking entry from netlink when synproxy is used. It was missing the addition of the synproxy extension. This was causing kernel crashes when a conntrack entry created by conntrackd was used after the switch of traffic from active node to the passive

Re: [PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-11 Thread Jesper Dangaard Brouer
On Thu, 11 May 2017 15:22:55 +0200 Eric Leblond wrote: > This patch fixes the creation of connection tracking entry from > netlink when synproxy is used. It was missing the addition of > the synproxy extension. > > This was causing kernel crashes when a conntrack entry created

[PATCH] netfilter: synproxy: fix conntrackd interaction

2017-05-11 Thread Eric Leblond
This patch fixes the creation of connection tracking entry from netlink when synproxy is used. It was missing the addition of the synproxy extension. This was causing kernel crashes when a conntrack entry created by conntrackd was used after the switch of traffic from active node to the passive