Date: Tue, 11 Apr 2017 08:47:36 +0200 From: "Kristof Provost" <kristof@sigsegv.be> To: peter.blok@bsd4all.org Cc: "Pavel Timofeev" <timp87@gmail.com>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: VNET branch destiny Message-ID: <7B9879DE-7500-47CB-8471-38E2B899C324@sigsegv.be> In-Reply-To: <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org> References: <CAAoTqfuAvZfoC-j8JFTvrpxqFMM5DjxyDXgMhMZLj3DO2pCYTw@mail.gmail.com> <0136F3BE-4B47-4677-8D81-3FE0F5E67E79@lists.zabbadoz.net> <CAAoTqfvJ013NTQB75JeVCysfk-xk-hac-f73gXfvCt5bBo_QXA@mail.gmail.com> <CAAoTqfuQXvKAQNOwshY5mkt0dG7Z1jKC6Aae9TF4hum1aUrJsA@mail.gmail.com> <24B3E322-5B92-470D-A1D6-10DF8EF79490@bsd4all.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Apr 2017, at 12:10, peter.blok@bsd4all.org wrote: > There have been issues with pf if I recall correctly. I currently have > issues with stable, pf and vnet. There is an issue with pf table > entries when an interface is moved to a different vnet. > > Does anyone no if there is a specific fix for this that hasn’t been > ported to stable? I haven’t had the time to test this on current. > I’m currently aware of at least some issues with pf and vnet, even in CURRENT. Not that one though, so can you make sure there’s a bug report with as much detail as possible? Please also cc me (kp@freebsd.org) on the report. Thanks, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B9879DE-7500-47CB-8471-38E2B899C324>