From owner-freebsd-mobile@FreeBSD.ORG Sat May 20 15:47:48 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D176A16A429 for ; Sat, 20 May 2006 15:47:48 +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 25ABD43D45 for ; Sat, 20 May 2006 15:47:47 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.88.34] (may be forged)) by msrv.matik.com.br (8.13.6/8.13.1) with ESMTP id k4KFleNC055890; Sat, 20 May 2006 12:47:41 -0300 (BRT) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-mobile@freebsd.org Date: Sat, 20 May 2006 12:47:26 -0300 User-Agent: KMail/1.9.1 References: <7.0.1.0.1.20060517080119.01e00df8@live555.com> <7.0.1.0.1.20060519133359.02083d70@live555.com> <446F2312.3000708@errno.com> In-Reply-To: <446F2312.3000708@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605201247.27862.asstec@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.1.0 X-Spam-Checker-Version: Antispam Datacenter Matik msrv.matik.com.br X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: More 'resource' problems with "ath0" X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 15:47:51 -0000 On Saturday 20 May 2006 11:09, Sam Leffler wrote: > > > Also, do you think that Joao's suggestion - copied below - is worth > > trying? > > No. The problem is in the driver (probably in the handling of packets > buffered for clients operating in ps mode). > it happens also when the powersave mode definitly is off, on the server, on= =20 the client and on the AP and is not only an issue on WL cards but also on=20 other NICs the problem appears more frequent when you have cybercoffees connected wher= e=20 games cause high udp/icmp broadcast traffic and probably attract similar=20 traffic coming back from the outside imediatly you see then such error messages you posted and services like nam= ed,=20 dhcpd, squid and other which use udp ports may be compromised what I posted certainly is a valid workaround on your server where the prob= lem=20 ocurrs, you can set values runtime to your needs and see no more errors=20 instantly sysctl net.inet.udp.recvspace=3D65536 sysctl net.inet.udp.maxdgram=3D131072=20 in addition you should consider blocking all broadcasts and 0's on your=20 network which will help a lot, you also may consider ingress filtering for= =20 smurf like traffic on your router in order to prevent this problems Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br