From owner-freebsd-pf@freebsd.org  Mon Jun 29 09:12:49 2015
Return-Path: <owner-freebsd-pf@freebsd.org>
Delivered-To: freebsd-pf@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DAA098C7E2
 for <freebsd-pf@mailman.ysv.freebsd.org>; Mon, 29 Jun 2015 09:12:49 +0000 (UTC)
 (envelope-from freebsd-pf@dino.sk)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9FDD61AC2
 for <freebsd-pf@freebsd.org>; Mon, 29 Jun 2015 09:12:48 +0000 (UTC)
 (envelope-from freebsd-pf@dino.sk)
Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Mon, 29 Jun 2015 11:12:46 +0200
 id 000F19B0.55910C0E.00002D83
Date: Mon, 29 Jun 2015 11:12:45 +0200
From: Milan Obuch <freebsd-pf@dino.sk>
To: Daniel Hartmeier <daniel@benzedrine.ch>
Cc: Ian FREISLICH <ian.freislich@capeaugusta.com>,
  freebsd-pf@freebsd.org
Subject: Re: Large scale NAT with PF - some weird problem
Message-ID: <20150629111245.2fab747c@zeta.dino.sk>
In-Reply-To: <20150629090448.GB22693@insomnia.benzedrine.ch>
References: <14e119e8fa8.2755.abfb21602af57f30a7457738c46ad3ae@capeaugusta.com>
 <E1Z6dHz-0000uu-D8@clue.co.za> <E1Z6eVg-0000yz-Ar@clue.co.za>
 <20150621195753.7b162633@zeta.dino.sk>
 <E1Z7Ixx-0006K1-5p@clue.co.za> <E1Z7K1Y-0006Ph-ON@clue.co.za>
 <20150623112331.668395d1@zeta.dino.sk>
 <20150628100609.635544e0@zeta.dino.sk>
 <20150629082654.GA22693@insomnia.benzedrine.ch>
 <20150629105201.7ee24e38@zeta.dino.sk>
 <20150629090448.GB22693@insomnia.benzedrine.ch>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; i386-portbld-freebsd10.1)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf/>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2015 09:12:49 -0000

On Mon, 29 Jun 2015 11:04:48 +0200
Daniel Hartmeier <daniel@benzedrine.ch> wrote:

> On Mon, Jun 29, 2015 at 10:52:01AM +0200, Milan Obuch wrote:
> 
> > Does this answerred your question fully or something more would be
> > usefull?
> 
> Which one is the magical IP address, i.e. the one that causes trouble
> once it's being used (I guess from x.y.26.0/27)?
> 
> It's always the same one, even across reloads and reboots?
> 
> Daniel

x.y.27.152, it was always the same, it kept reappear randomly. Now,
with pool reduced to x.y.26.0/24 it can't happen, maybe for some time
this workaround will be enough. If, however, anybody would like to test
something, it can be changed for test again.

I did not observed this behaviour with any other IP after I upgrade to
10.2-PRERELASE, but I remember seeing this issue with x.y.27.153 and
x.y.27.154, just less frequently. Most of the time I just looked for
x.y.27.152, nothing more was necessary.

Milan