From owner-freebsd-stable@freebsd.org Sun Jul 22 13:53:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 802D9104C3F0 for ; Sun, 22 Jul 2018 13:53:53 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [IPv6:2a01:4f8:150:80b1:fe57:f772:524c:99d0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1398375C63 for ; Sun, 22 Jul 2018 13:53:52 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:106d:4420:df9b:a36f:cb77:f65e]) by madarka.gustik.eu (Postfix) with ESMTPSA id 27A0F165CD for ; Sun, 22 Jul 2018 15:53:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1532267623; bh=pTnw1qsEY9neia+96hYeMYofrdznwxDdMs3R5Uh9kXg=; h=Date:From:To:Subject; b=v5GbsfPaa/ROIotgK9SiWROP3TxrVNQgxnKI1G8IXlhFwYoTKR4XF0Yg5tPF8EfLY 32Ug4H8Uhs3oCd1f2u+wdZsMIGMB8Or3y0/+SFTjuPsjLPsPZe2xm+IZWFIG7OoFRY LvewTP3KxPnCDqOBxTP7OetM43/YkzvCXM0bLlV4= Date: Sun, 22 Jul 2018 15:53:41 +0200 From: Lars Schotte To: freebsd-stable@freebsd.org Subject: PF problems with 11-stable Message-ID: <20180722155341.065c3d4d@romy.j20.helspy.pw> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2018 13:53:53 -0000 Hey, I am on 11.2-STABLE FreeBSD 11.2-STABLE #9 r336597 Sun Jul 22 14:08:38 CEST 2018 and I see 2 problems with PF that are still there: 1.) set skip on lo does not work even though ifconfig lo matches. SOLVED TEMPORARILY BY: set skip on lo0 2.) synproxy state needs no explanation. Problem still persists. SOLVED TEMPORARILY BY: keep state everywhere. -- Lars Schotte Mudroňova 13 92101 Piešťany