From owner-freebsd-current@freebsd.org Fri May 20 12:03:35 2016 Return-Path: Delivered-To: freebsd-current@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 274ACB43D4D for ; Fri, 20 May 2016 12:03:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 7D1361D68 for ; Fri, 20 May 2016 12:03:33 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1b3j9P-000cw2-Os>; Fri, 20 May 2016 14:03:31 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=hermann) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from ) id <1b3j9P-0023pC-H7>; Fri, 20 May 2016 14:03:31 +0200 Date: Fri, 20 May 2016 14:01:52 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: CURRENT: ipfw: problems with timeouts and worse network performance Message-ID: <20160520140152.3ab6fe44@hermann> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2016 12:03:35 -0000 With most recent CURRENT (r300295) I face a very strange behaviour on all systems running CURRENT with IPFW enabled. I realize massive network problems, especially when services like claws-mail, pgadmin3, OpenLDAP clients, drill or even svn try to connect to their servers. In most cases, the connection couln't be established due to timeouts, but repeating, like performing svn in /usr/src gives some results, but this is highly erratic. The problems vanishes when "ipfw disable firewall" is entered. We use both custom ipfw-rule-scripts as well as those used with rc.conf (mostly type WORKSTATION). The problem is prominet with having /usr/src and /usr/ports updated via subversion. In 99% of the cases svn drops out with timeouts in case IPFW is active - but everything seems all right when ipfw is disabled. As far as I could see this problem affects all CURRENT we use and it is not NIC specific, but sticks with IPFW. I reported earlier about broken pipes in ssh sessions to remote hosts, which occur on an erratic basis. i'm investigating this problem now and it seems that it is also ipfw-related, but I'm not sure. This problem is present since a couple of weeks now. Is there anything known about ipfw problems? Kind regards, Oliver