Date: Mon, 29 Dec 2014 20:02:45 -0500 From: Jason Healy <jhealy@logn.net> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-net@freebsd.org Subject: Re: IPv6 routes leaking between FIBs? Message-ID: <BE5A91D7-2D30-4987-A077-32425C2C2549@logn.net> In-Reply-To: <DC4844DB-53FE-4C2A-AE3B-75E08E273866@lists.zabbadoz.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE5A91D7-2D30-4987-A077-32425C2C2549>