From owner-freebsd-amd64@freebsd.org Sun Dec 4 12:37:48 2016 Return-Path: Delivered-To: freebsd-amd64@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 11434C586C4 for ; Sun, 4 Dec 2016 12:37:48 +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 EBF6B14FF for ; Sun, 4 Dec 2016 12:37:47 +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 uB4CblR1015188 for ; Sun, 4 Dec 2016 12:37:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215041] [pf] Handshake to certain (fixed) hosts is dropped Date: Sun, 04 Dec 2016 12:37:47 +0000 X-Bugzilla-Reason: CC 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: bsd@ddh.de1.cc 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 cc attachments.created 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-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2016 12:37:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215041 Bug ID: 215041 Summary: [pf] Handshake to certain (fixed) hosts is dropped Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: bsd@ddh.de1.cc CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 177653 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177653&action= =3Dedit Captures from internal interfaces, external interface, and PF (The same behavior was observed on 10.3-RELEASE, but remained unchanged aft= er upgrading to 11-RELEASE) I am running a bridge configured as follows: cloned_interfaces=3D"bridge0" ifconfig_bridge0=3D"addm em0 addm re0 SYNCDHCP" ifconfig_em0=3D"up -tso" # Internal interface ifconfig_re0=3D"up -tso" # External interface, connecting to NAT router And this extremely minimal firewall config: pass log all The issue is that while PF is running, a host connected to the internal interface attempting to connect to 185.60.115.40:443 (something related to = the login of Blizzard's battle.net service), will not receive a response to the initial SYN packet, see em0.pcap in the attached zip. However, on the exter= nal interface (see re0.pcap) the SYN/ACKs do plainly show up, both for the init= ial SYN an the retries. The logs of PF itself align with the view of the intern= al interface, the SYN/ACKs do not show up at all: 00:00:00.000000 rule 0..16777216/0(match): pass in on re0: 192.168.0.186.56= 465 > 185.60.115.40.443: Flags [S], seq 1914506337, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 00:00:00.000058 rule 0..16777216/0(match): pass out on bridge0: 192.168.0.186.56465 > 185.60.115.40.443: Flags [S], seq 1914506337, win 819= 2, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 00:00:00.250999 rule 0..16777216/0(match): pass in on re0: 192.168.0.186.56= 467 > 185.60.115.40.443: Flags [S], seq 2119186033, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0 00:00:00.000059 rule 0..16777216/0(match): pass out on bridge0: 192.168.0.186.56467 > 185.60.115.40.443: Flags [S], seq 2119186033, win 819= 2, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0# Disabling PF via "pfctl -d" instantly makes the problem disappear, "pfctl -= e" makes it reappear just as reliably, so the issue definitely seems to be lin= ked to PF and not a general networking or hardware/driver problem. --=20 You are receiving this mail because: You are on the CC list for the bug.=