From owner-freebsd-net@FreeBSD.ORG  Tue Dec 30 01:02:47 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 38DC737B;
 Tue, 30 Dec 2014 01:02:47 +0000 (UTC)
Received: from omicron.logn.net (omicron.logn.net [72.10.118.7])
 by mx1.freebsd.org (Postfix) with ESMTP id 1256A1C95;
 Tue, 30 Dec 2014 01:02:46 +0000 (UTC)
Received: from [10.3.73.86] (unknown [10.3.73.86])
 by omicron.logn.net (Postfix) with ESMTPSA id 7E7C94A0082;
 Mon, 29 Dec 2014 20:02:45 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: IPv6 routes leaking between FIBs?
From: Jason Healy <jhealy@logn.net>
In-Reply-To: <DC4844DB-53FE-4C2A-AE3B-75E08E273866@lists.zabbadoz.net>
Date: Mon, 29 Dec 2014 20:02:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE5A91D7-2D30-4987-A077-32425C2C2549@logn.net>
References: <C2295EFD-C052-438B-8524-974C17E1FBB6@logn.net>
 <54A0F4A7.5020502@freebsd.org>
 <ECBB89C5-05F4-464B-AE40-6EA446E516DD@logn.net>
 <54A1A8D2.9080704@freebsd.org>
 <DC4844DB-53FE-4C2A-AE3B-75E08E273866@lists.zabbadoz.net>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-Mailer: Apple Mail (2.1878.6)
Cc: freebsd-net@freebsd.org
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 01:02:47 -0000

On Dec 29, 2014, at 2:34 PM, Bjoern A. Zeeb =
<bzeeb-lists@lists.zabbadoz.net> wrote:

> pf and VNETs are a cause for panic at the moment;  don=92t go that =
route (yet).

Good to know.

With that in mind, I think my best workaround for now is to disable IPv6 =
on the management interface, leaving the transit interface as the only =
one with a v6 address assigned.  This effectively isolates it from the =
rest of the box, and I=92ll just have to manage the box itself via v4 =
for the time being until the v6 fibs get fixed.

Meanwhile, I=92ve created PR 196361 to track the underlying issue:

  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196361

I=92ll keep working to spin up PF on the box and I=92ll let you know if =
I bump into any other issues.

Thanks for the guidance,

Jason