From owner-freebsd-mobile@FreeBSD.ORG Fri Apr 7 03:20:06 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 966C916A40B for ; Fri, 7 Apr 2006 03:20:06 +0000 (UTC) (envelope-from pconover@ipro.net) Received: from ipro.net (mail.ipro.net [68.216.93.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D7F743D67 for ; Fri, 7 Apr 2006 03:20:01 +0000 (GMT) (envelope-from pconover@ipro.net) Received: from 12.202.236.24 with HTTP by webserver ipro.net (68.216.93.17) ; Thu, 6 Apr 2006 23:23:52 EDT Date: Thu, 6 Apr 2006 23:23:52 -0400 Message-Id: <200604062323.AA529400352@ipro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: "P C" To: X-Mailer: Subject: Re: Atheros ad-hoc driver bug status? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pconover@ipro.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 03:20:06 -0000 I've tested Ad-Hoc mode on Atheros based CM9 and EMP-8602 with several WRAP 1.11 units running pfSense latest betas and alphas. Always the same result: extremely slow transfers. A pfSense Admin/Dev reported the same finding: " Yes, there is a driver bug in adhoc mode. Performance is terrible. Not sure why yet. " -[lsf] They seem to keep their freeBSD versions Very up to date. -pc ________________________________________________________________ Sent via the WebMail system at ipro.net