From owner-freebsd-pf@FreeBSD.ORG Fri Aug 16 17:12:55 2013 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6B0B88C6 for ; Fri, 16 Aug 2013 17:12:55 +0000 (UTC) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (cust.static.213-3-30-106.swisscomdata.ch [213.3.30.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD9DB250F for ; Fri, 16 Aug 2013 17:12:53 +0000 (UTC) Received: from insomnia.benzedrine.cx (localhost [127.0.0.1]) by insomnia.benzedrine.cx (8.14.6/8.14.5) with ESMTP id r7GHCRwc026232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Aug 2013 19:12:28 +0200 (MEST) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.14.6/8.14.5/Submit) id r7GHCRnt012871; Fri, 16 Aug 2013 19:12:27 +0200 (MEST) Date: Fri, 16 Aug 2013 19:12:27 +0200 From: Daniel Hartmeier To: Alexander Subject: Re: Windows 7 + freebsd-pf + windows scale SYN-ACK problem Message-ID: <20130816171227.GB28156@insomnia.benzedrine.cx> References: <520E1822.7010505@yandex.ru> <20130816125058.GA28156@insomnia.benzedrine.cx> <520E35B3.4080607@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <520E35B3.4080607@yandex.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-pf@freebsd.org X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 16 Aug 2013 17:12:55 -0000 On Fri, Aug 16, 2013 at 06:22:43PM +0400, Alexander wrote: > My connection with server (port 6666) starts to work and i think i > can be satisfied by this solution. But i still cannot understand why > packets are dropped without no state rules. As i revealed they are > dropped between bridge0 and vlan 1 interfaces. This is probably because you filter on bridge0. There are some sysctl's related to this, run sysctl -a | grep bridge I think in some combinations, pf sees packets on the bridge interface with the wrong direction. Do you have a particular reason for filtering on the bridge interface, and not just on the physical interfaces? Daniel