From owner-freebsd-stable@FreeBSD.ORG Fri May 28 11:20:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD3E6106564A for ; Fri, 28 May 2010 11:20:53 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id 753B38FC15 for ; Fri, 28 May 2010 11:20:53 +0000 (UTC) Received: from vampire.homelinux.org (dslb-088-066-001-178.pools.arcor-ip.net [88.66.1.178]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MfVBH-1Nt1qR1DkB-00OxW8; Fri, 28 May 2010 13:20:52 +0200 Received: (qmail 33557 invoked from network); 28 May 2010 11:20:51 -0000 Received: from f8x64.laiers.local (192.168.4.188) by ns1.laiers.local with SMTP; 28 May 2010 11:20:51 -0000 From: Max Laier Organization: FreeBSD To: Giulio Ferro Date: Fri, 28 May 2010 13:20:50 +0200 User-Agent: KMail/1.13.3 (FreeBSD/8.0-RELEASE-p2; KDE/4.4.3; amd64; ; ) References: <4BFF589F.2050102@zirakzigil.org> In-Reply-To: <4BFF589F.2050102@zirakzigil.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005281320.51027.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1+EZC8zZ1kgSau2UcgSM49rAtyShVyWjIcycIk K9LJTbHdcZ1xGKWRniWraptDGe1fpYg/88Kju1glv99KRGsjHP Er5rWXjlV6FMk/oRcpRaw== Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: PF + BRIDGE still causes system freezing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2010 11:20:53 -0000 On Friday 28 May 2010 07:46:07 Giulio Ferro wrote: > Months ago I reported a system freezing whenever bridge was used > with pf. This still happens now in 8.1 prerelease: after several minutes > to hours > that the bridge is active the system becomes unresponsive. as I told you last time your reported this problem: you need to simplify your setup in order to track down the problem. For all I know, you have created a routing or ethernet loop that is the cause of your problems. Unless you can provide a simple setup that can be reproduced, you have to track down the issue yourself - sorry. Max