From owner-freebsd-current@FreeBSD.ORG Thu Jun 23 21:29:58 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 2C58016A442 for ; Thu, 23 Jun 2005 21:29:58 +0000 (GMT) (envelope-from snow+freebsd-current@teardrop.org) Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E8843D55 for ; Thu, 23 Jun 2005 21:29:57 +0000 (GMT) (envelope-from snow+freebsd-current@teardrop.org) Received: by imladris.teardrop.org (Postfix, from userid 100) id EFAEEBF787; Thu, 23 Jun 2005 17:31:39 -0400 (EDT) Date: Thu, 23 Jun 2005 17:31:39 -0400 From: James Snow To: Wilko Bulte Message-ID: <20050623213139.GA73882@teardrop.org> References: <20050621205048.GA61951@freebie.xs4all.nl> <050622074135F.25017@www.mmlab.cse.yzu.edu.tw> <20050623202416.GA64730@freebie.xs4all.nl> <20050623204325.GA72574@teardrop.org> <20050623211620.GA65274@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050623211620.GA65274@freebie.xs4all.nl> User-Agent: Mutt/1.4.2.1i Cc: Tai-hwa Liang , freebsd-current@freebsd.org Subject: Re: Getting WPA to work on ath(4) 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: Thu, 23 Jun 2005 21:29:58 -0000 On Thu, Jun 23, 2005 at 11:16:20PM +0200, Wilko Bulte wrote: > > How do you disable WME? [ I feel stranded in a maze of acronyms, all > different :-) ] ifconfig -wme I think it's in the ifconfig man page, but I reserve the right to be wrong. If it's not, it clearly should be. My understanding is that we do something wrong with WME right now, and this in turn makes APs unhappy with us. > I noticed today that wpa_supplicant renegotiated multiple times even with > SSID broadcasting enabled. So it was most definitely not the full > fix to enable broadcasting. Well, we also shouldn't have to enable broadcasting to get wpa_supplicant to work. I exchanging emails with Sam Leffler about this, but he's on vacation this week. -Snow