From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 3 22:28:04 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4CFB106566C for ; Thu, 3 Sep 2009 22:28:04 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail4.es.net [IPv6:2001:400:6000:6::2]) by mx1.freebsd.org (Postfix) with ESMTP id 964FD8FC1A for ; Thu, 3 Sep 2009 22:28:04 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n83MS1sF005515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Sep 2009 15:28:02 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 528461CC09; Thu, 3 Sep 2009 15:28:01 -0700 (PDT) To: "Richard Kolkovich" In-reply-to: Your message of "Thu, 03 Sep 2009 17:21:57 CDT." <20090903222156.GA6786@magus.portal.sigil.org> Date: Thu, 03 Sep 2009 15:28:01 -0700 From: "Kevin Oberman" Message-Id: <20090903222801.528461CC09@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-09-04_01:2009-09-01, 2009-09-04, 2009-09-03 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0909030161 Cc: Dan Langille , freebsd-mobile@freebsd.org Subject: Re: ath0 link up/down frequent 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: Thu, 03 Sep 2009 22:28:05 -0000 > From: "Richard Kolkovich" > Date: Thu, 3 Sep 2009 17:21:57 -0500 > > On Sat, Aug 22, 2009 at 11:29:13AM -0700, Kevin Oberman wrote: > > > Anything I should look into? > > > > My standard suggestion, which works for me, is to issue an 'ifconfig > > ath0 -bgscan'. Background scanning is not supposed to effect the > > association, but it seems to, at least on my system. > > > > My experience has been much the same. It typically only happens in > areas with a lot of APs, though (i.e. my apartment building). My case is similar. I will see it on occasion at home where I typically see only two or three APs, but is only a real problem when I am at a networking conference and there are a whole raft of APs out there. In those cases the wireless is rendered unusable as I lose association every 5 minutes. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751