From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: [PATCH 2/2] extensions: restore matching any SPI id by default Date: Wed, 15 Jul 2015 19:30:35 +0200 Message-ID: <20150715173035.GA5675@salvia> References: <1436964819-28109-1-git-send-email-jengelh@inai.de> <1436964819-28109-3-git-send-email-jengelh@inai.de> <20150715162442.GA22476@salvia> <20150715165515.GA4177@salvia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@vger.kernel.org To: Jan Engelhardt Return-path: Received: from mail.us.es ([193.147.175.20]:56333 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751764AbbGORYx (ORCPT ); Wed, 15 Jul 2015 13:24:53 -0400 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Wed, Jul 15, 2015 at 07:10:29PM +0200, Jan Engelhardt wrote: > > On Wednesday 2015-07-15 18:55, Pablo Neira Ayuso wrote: > >> >> +-p esp -m esp;-p esp -m esp --espspi 0;FAIL > >> >> -p esp -m esp;=;OK > >> > > > > >Given that this is changing the behaviour again, I would suggest that > >-p esp -m esp displays -p -m esp --espspi 0:4294967295 via > >iptables-save. > > The printing via iptables -S was not the problem. > The patch is about that no AH/ESP packets were matched when using > just "-m esp" because of the implied --espspi 0:0. Without your patch: iptables -A INPUT -p ah # iptables-save ... -A INPUT -p ah -m ah --ahspi 0 With your patch: iptables -A INPUT -p ah iptables -A INPUT -p ah --ahspi 0:4294967295 # iptables-save ... -A INPUT -p ah -m ah -A INPUT -p ah -m ah what I'm suggesting is that this prints what it indeed does: # iptables-save ... -A INPUT -p ah --ahspi 0:4294967295