From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: xt_connlimit 20070625 Date: Thu, 28 Jun 2007 21:48:57 +0200 Message-ID: <468410A9.70309@trash.net> References: <467BAF07.6020502@trash.net> <467FA9CE.8000805@trash.net> <46840B9F.7080803@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Netfilter Developer Mailing List To: Jan Engelhardt Return-path: In-Reply-To: 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 Jan Engelhardt wrote: > On Jun 28 2007 21:27, Patrick McHardy wrote: > >>I though you would store the struct xt_connlimit_conn in the >>ct_extend area. > > > Ah, that was the big hint. Thank you. > I'll just put the pointer to xt_connlimit_data there. Just as easy. Actually my entire suggestion may be broken. We can't allocate extensions once the conntrack is confirmed. So this would only work for new connections.