From owner-freebsd-bugs@FreeBSD.ORG  Wed Mar 18 01:58:44 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6A1F6D6B
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Mar 2015 01:58:44 +0000 (UTC)
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 50839162
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Mar 2015 01:58:44 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2I1whoh005533
 for <freebsd-bugs@FreeBSD.org>; Wed, 18 Mar 2015 01:58:43 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 198674] [pf] [tftp-proxy] tftp-proxy cannot write rdr rules
Date: Wed, 18 Mar 2015 01:58:44 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jjasen@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
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-198674-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 01:58:44 -0000

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

            Bug ID: 198674
           Summary: [pf] [tftp-proxy] tftp-proxy cannot write rdr rules
           Product: Base System
           Version: 10.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: jjasen@gmail.com

In FreeBSD 10.1-RELEASE-p6, a rule similar to the below will result in no tftp
connection, and entries in /var/log/messages such as: 

"Mar 17 23:38:28 vm-fbd-fw-02 tftp-proxy[28376]: pf connection lookup failed
(no rdr?)"


rdr pass log on em0 proto udp from 10.0.0.0/24 to 10.0.0.5 port 69 \
   -> 127.0.0.1 port 6969

The error comes from:
/usr/src/contrib/pf/tftp-proxy.c:
"        /* find the un-rdr'd server and port the client wanted */
        if (server_lookup((struct sockaddr *)&from,
            (struct sockaddr *)&proxy, (struct sockaddr *)&server,
            IPPROTO_UDP) != 0) {
                syslog(LOG_ERR, "pf connection lookup failed (no rdr?)");
                exit(1); 
        }
"

This did not happen in FreeBSD 10.0.

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