From owner-freebsd-bugs@freebsd.org  Wed Oct 18 13:54:34 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 C5C95E39933
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 18 Oct 2017 13:54:34 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 B3E327E60D
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Oct 2017 13:54:34 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IDsYuu020871
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Oct 2017 13:54:34 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 223093] /dev/pf locks disrupt other pf-dependent services
 (ftp-proxy, tftp-proxy, relayd, pfctl, etc)
Date: Wed, 18 Oct 2017 13:54:34 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.4-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jjasen@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-223093-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Oct 2017 13:54:34 -0000

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

            Bug ID: 223093
           Summary: /dev/pf locks disrupt other pf-dependent services
                    (ftp-proxy, tftp-proxy, relayd, pfctl, etc)
           Product: Base System
           Version: 10.4-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: jjasen@gmail.com

A firewall system running pf, with ftp-proxy, tftp-proxy and relayd in acti=
ve
use can encounter conditions where one or more of the supporting services or
utilities will fail.

For example, while ftp-proxy has a lock on /dev/pf, relayd cannot make chan=
ges
and will crash (reference bug 213859).=20

Additionally, if tftp-proxy has a lock on /dev/pf, the ftp-proxy connection
will fail. Conversely, if something has a lock on /dev/pf, tftp-proxy will
abort and retry.

--=20
You are receiving this mail because:
You are the assignee for the bug.=