From owner-freebsd-ipfw@FreeBSD.ORG Fri Mar 14 07:46:30 2008 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC48C106566B for ; Fri, 14 Mar 2008 07:46:30 +0000 (UTC) (envelope-from asstec@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 611158FC1A for ; Fri, 14 Mar 2008 07:46:29 +0000 (UTC) (envelope-from asstec@matik.com.br) Received: from ap-h.matik.com.br (ap-h.p.matik.com.br [200.152.83.36] (may be forged)) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id m2E7kRvU075931; Fri, 14 Mar 2008 04:46:28 -0300 (BRT) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-ipfw@freebsd.org Date: Fri, 14 Mar 2008 04:47:18 -0300 User-Agent: KMail/1.9.7 References: <1205343184.4032.44.camel@wade-linux.itiva.com> <200803131441.36597.asstec@matik.com.br> <1205442400.4349.18.camel@wade-linux.itiva.com> In-Reply-To: <1205442400.4349.18.camel@wade-linux.itiva.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200803140447.18646.asstec@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Cc: Wade Klaver Subject: Re: On the trail of a dummynet/bridge/ipfw bug. X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 07:46:31 -0000 On Thursday 13 March 2008 18:06:40 Wade Klaver wrote: > OK, here's something weird then. ipfw pipe show | wc -l has reported > higher numbers: > [root@ibm3550b ~]# ipfw pipe show | wc -l > 3453 > This was reported after the bridge "died" attempting 2600 simultaneous > connections... it had been running at 2400 before I added 200 more. > Now, immediately after the above crash, I do a /etc/rc.d/netif restart, > and then: > [root@ibm3550b ~]# ipfw pipe show | wc -l > 3900 > Then as long as I add additional connections very slowly, I can manage > to get more established until it dies at 2800 with: > [root@ibm3550b ~]# ipfw pipe show | wc -l > 4160 > At this point I am only using these numbers as a general indication of > pipe activity as the output is not 1 pipe per line. In fact there is > more often than not two lines per pipe. However, the end problem > remains the same. After a point, the bridge doesn't get saturated, it > crashes and requires that the network be restarted before continuing. > The fact that it is necessary only to restart the network and not to > flush ipfw's pipes (which has no effect without a network restart) > perhaps suggests the problem lies in a different subsystem? The > broadcom driver perhaps? hard to say because you do not tell so very much about your machine, it mig= ht=20 be too weak for so many pipes (mem or cpu?), I do not know your setup or th= e=20 nics you use you say it crash but can restart the network? probably you have some error = in=20 your script or since you run bridge some mac issue? =2D-=20 Participe no BAIXO ASSINADO SCM: http://info.matik.com.br =2D- Atenciosamente, J.M. Respons=E1vel Plant=E3o Site Support Matik Infomatik Internet Technology (18)3551.8155 =A0(18)8112.7007 A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br