From owner-freebsd-bugs@freebsd.org Fri Mar 17 23:13:19 2017 Return-Path: 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 97BFED1005C for ; Fri, 17 Mar 2017 23:13:19 +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 6AEA71268 for ; Fri, 17 Mar 2017 23:13:19 +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 v2HNDJMR060097 for ; Fri, 17 Mar 2017 23:13:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217883] IPv6 with route_to broken with introduction of PF_FWD Date: Fri, 17 Mar 2017 23:13:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vegeta@tuxpowered.net 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 23:13:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217883 Bug ID: 217883 Summary: IPv6 with route_to broken with introduction of PF_FWD Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: vegeta@tuxpowered.net Introducing another direction "PF_FWD" broke possibility of forwarding IPv6 traffic if firewall has direction-matching rule on outgoing interface. In my case on public interface of a LoadBalancer has a rule witch catches t= he traffic and uses route_to to direct it to one of hosts inside network. Inte= rnal interface of this LoadBalancer has a rule "pass out quick on $if_intern_all keep state (tcp.first 5 tcp.opening 5)". Since this rule only passes direct= ion PF_OUT, a IPv6 packet of direction PF_FWD won't match this rule. Traffic is then properly dropped on the last rule of my firewall. Observing dropped traffic on pflog0 shows that the direction PF_FWD is kept and even in the e= nd show by tcpdump as "unk(3)". There are a few ways to solve it: 1. Teach tcpdump about PF_FWD, make pf_test_rule match packets with directi= on PF_FWD on rules with PF_OUT. https://github.com/innogames/freebsd/commit/581c3c88f460f6747c342f8a059d3cb= 92b8e155f https://github.com/innogames/freebsd/commit/7273dc2abac6c16ecaf28b63be69d3a= 1635a441f 2. Extend it even more, use PF_FWD for IPv4 too and teach pfctl to understa= nd new direction "forward". That of course would break all firewall rules every written in the human history. 3. Or the simplest way: present direction PF_OUT to pf_test_rule no matter = if PF_FWD was used or not: https://github.com/innogames/freebsd/commit/17a7601573372ac76f624e27d16936d= bb80012e1 --=20 You are receiving this mail because: You are the assignee for the bug.=