From owner-freebsd-current@FreeBSD.ORG Wed Jul 6 01:40:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35E1616A41C for ; Wed, 6 Jul 2005 01:40:40 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E407843D45 for ; Wed, 6 Jul 2005 01:40:39 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 7FD00507307; Wed, 6 Jul 2005 09:40:36 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 7ACA25072F1; Wed, 6 Jul 2005 09:40:36 +0800 (CST) Date: Wed, 6 Jul 2005 09:40:36 +0800 (CST) From: Tai-hwa Liang To: Sam Leffler In-Reply-To: <42CAB549.7010409@errno.com> Message-ID: <05070609391811.747@www.mmlab.cse.yzu.edu.tw> References: <200507051430.04322.jhugo@icomtek.csir.co.za> <42CAB549.7010409@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Johann Hugo Subject: Re: ath client loose connection to ath hostap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 06 Jul 2005 01:40:40 -0000 On Tue, 5 Jul 2005, Sam Leffler wrote: > Johann Hugo wrote: >> Hi >> I have 2x soekris 4501 units with atheros adapters, 1=hostap mode, >> 1=client. >> With a continues ping, everything keeps running (16+ hours), but after an >> inactive period they lose connectivity. The client still reports it is >> associated, but there is no IP connectivity. After "ath down" + "ath up" it >> does not want to associated with hostap any more. After client reboot it >> works fine again. After inactive period - same problem. > > I believe Tai-hwa Liang has a fix for this pending re approval. You're > seeing beacon misses on the client but when the client scans to reassociate > it bogusly creates a new entry in the scan cache and things get confused. If > his commit doesn't fix your problem check on the ap side to see if there are > auth+associate requests coming in when you get a beacon miss on the client. Just committed to sys/net80211/ieee80211_input.c:1.56. Please cvsup later. Thanks, Tai-hwa Liang