From owner-freebsd-pf@FreeBSD.ORG Mon Jun 23 22:31:31 2014 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2BB34BB for ; Mon, 23 Jun 2014 22:31:31 +0000 (UTC) Received: from ns1.ogris.net (ns1.ogris.net [IPv6:2a00:1348::17:0:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id ACF5E2C64 for ; Mon, 23 Jun 2014 22:31:31 +0000 (UTC) Received: from [IPv6:2a00:1348:0:5::a] (core7.intra.ogris.net [IPv6:2a00:1348:0:5::a]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ns1.ogris.net (Postfix) with ESMTPSA id 2F5D62B71E8 for ; Tue, 24 Jun 2014 00:31:23 +0200 (CEST) Message-ID: <53A8AABA.1050801@ogris.de> Date: Tue, 24 Jun 2014 00:31:22 +0200 From: "Felix J. Ogris" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-pf@freebsd.org Subject: rdr inet6 to local ftp-proxy sends tcp rst to client Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 22:31:32 -0000 Hi, this rule doesn't redirect as expected, but sends tcp rst with incorrect checksum to the client: rdr on $lanif inet6 proto tcp from port >= 1024 to port ftp -> ($lanif) port ftp-proxy Neither does "rdr pass ..." nor if I redirect to (lo) or ::1 or to the globally scoped ipv6 address bound to $lanif. The redirected connection never hits the userspace (verified with 'nc -6 -l'). pfctl -s states reports: all tcp $lanif[8021] ($ftpserver[21]) <- $client[some high port] SYN_SENT:ESTABLISHED sockstat -6 is confused: ? ? ? ? tcp6 $lanif:8021 $client:some_high_port Same behaviour on 9.2-RELEASE i386 and 10.0-RELEASE amd64. Rule has worked for years with ipv4. Maybe related to kern/179392. --Felix