From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 21 17:29:13 2008 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 7CA7B106564A for ; Sun, 21 Sep 2008 17:29:13 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 3A4DF8FC1D for ; Sun, 21 Sep 2008 17:29:13 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so251754ele.13 for ; Sun, 21 Sep 2008 10:29:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=g8kCnGgmeMTG/0J0s7WtY046bteuRoBWPe5yLAXne9I=; b=MWWoix814Ai7cRRPgXGzkB8t9pjTJDxoPE2MZjUm5Tt1/gkI+prUHEHGwQKomx9TVG xNhe7fIQCOVSn/GnH6+pl89V0YT0sVt/TKLrzv2oirg1//OAgNFHZbuip8Uc1mkAb2aj bEs36iBRtveupZBRGWZJkl00krBotf6v/Zv10= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=fONJjOPYv0O6P0j+fOwUb0/Pg0Oyjwocqb8Suy/cISdtZkV9kTa2vXp5k3iXZjM/yb AZW09IaxbY/28TBbtrxyNp3Us2EvhlMsCIcRuUtVhKyAGTFGkt04jhL7/ionY6FbFyqQ suvSxQYzLl+IEnB+327JFNP6GjSfXMBaFsjgA= Received: by 10.151.156.19 with SMTP id i19mr5980119ybo.45.1222016568466; Sun, 21 Sep 2008 10:02:48 -0700 (PDT) Received: by 10.151.26.16 with HTTP; Sun, 21 Sep 2008 10:02:48 -0700 (PDT) Message-ID: Date: Sun, 21 Sep 2008 21:02:48 +0400 From: "Nikolay Tychina" To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Aser Aspire 5520's ACPI asl 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: Sun, 21 Sep 2008 17:29:13 -0000 Hello, i have problems with acpi on my Acer Aspire 5520. If anybody hasn't annoying console acpi error messages and has acpi works well, please, send me your .asl : # acpidump -dt > *name*-*system*.asl I will try compile it and use new DSDT. TNA, Nikolay. From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 22 13:25:05 2008 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 348D41065671 for ; Mon, 22 Sep 2008 13:25:05 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5EC9E8FC18 for ; Mon, 22 Sep 2008 13:25:04 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id D810933CD3; Mon, 22 Sep 2008 15:25:00 +0200 (SAST) Date: Mon, 22 Sep 2008 15:25:00 +0200 From: John Hay To: freebsd-mobile@freebsd.org Message-ID: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: setting bssid in adhoc mode 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: Mon, 22 Sep 2008 13:25:05 -0000 Hi I'm trying out the new ath/wlan stuff in current. Should one still be able to set the bssid in adhoc mode? We normally lock the bssid in an adhoc network because of problems that the network split and does not merge, if you do not do it. What I have done is this: # ifconfig wlan0 create wlandev ath0 wlanmode adhoc # ifconfig wlan0 ssid ptamesh up Up to here works well. It will scan and if it finds another node with the same ssid, it will "lock" on that channel and use the correct bssid. If it does not find another node with the same ssid, it will start it own thing on channel 10. But it looks like one cannot set the bssid. # ifconfig wlan0 bssid 02:07:ca:fe:ba:be ifconfig: 02:07:ca:fe:ba:be: bad value So should it work or should I do it in a different way? I saw a wlanbssid command in the ifconfig man page, but it does not seem to do anything. I tried it like this: # ifconfig wlan0 create wlandev ath0 wlanmode adhoc wlanbssid 02:07:ca:fe:ba:be It did not give an error, but also did not lock the bssid. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 22 15:48:23 2008 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 1B827106566B for ; Mon, 22 Sep 2008 15:48:23 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id EB4228FC08 for ; Mon, 22 Sep 2008 15:48:22 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8MFmMWN059167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Sep 2008 08:48:22 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48D7BE46.10306@freebsd.org> Date: Mon, 22 Sep 2008 08:48:22 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: John Hay References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> In-Reply-To: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Mon, 22 Sep 2008 15:48:23 -0000 John Hay wrote: > Hi > > I'm trying out the new ath/wlan stuff in current. Should one still be > able to set the bssid in adhoc mode? We normally lock the bssid in > an adhoc network because of problems that the network split and does > not merge, if you do not do it. > > What I have done is this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > # ifconfig wlan0 ssid ptamesh up > > Up to here works well. It will scan and if it finds another node with the > same ssid, it will "lock" on that channel and use the correct bssid. > > If it does not find another node with the same ssid, it will start it > own thing on channel 10. But it looks like one cannot set the bssid. > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > ifconfig: 02:07:ca:fe:ba:be: bad value > > So should it work or should I do it in a different way? I saw a > wlanbssid command in the ifconfig man page, but it does not seem to > do anything. I tried it like this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc wlanbssid 02:07:ca:fe:ba:be > > It did not give an error, but also did not lock the bssid. > > It should be possible to alter the bssid. wlanbssid is used to fix the bssid/mac address of the vap at create. Sam From owner-freebsd-mobile@FreeBSD.ORG Wed Sep 24 01:08:27 2008 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 6B1381065688 for ; Wed, 24 Sep 2008 01:08:27 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 424928FC1F for ; Wed, 24 Sep 2008 01:08:26 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KiIby-0003Ht-9r for freebsd-mobile@freebsd.org; Tue, 23 Sep 2008 17:52:10 -0700 Message-ID: <19639964.post@talk.nabble.com> Date: Tue, 23 Sep 2008 17:52:10 -0700 (PDT) From: Jakub Lach To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jakub_lach@mailplus.pl Subject: 7 STABLE on Fujitsu Siemens E8420/E8410 /Lenovo T61 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: Wed, 24 Sep 2008 01:08:27 -0000 Hi. I'm going to buy notebook soon. My basic requirments are: -robust construction -FreeBSD amd64 7 STABLE OS -2GB+/4GB RAM, preferably DDR3 -working sound, wifi -working PCMCIA -working Speedstep -working temperature monitoring (mbmon or similar) -moderate power consumption -fast core 2 penryn cpu Since nvidia driver doesn't support amd64, their cards are out of question. Moreover, there are heat/voltage problems with them recently. E8420 is using Intel GMA X4500 HD, will it work with FreeBSD? I've found this: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=1cfe769c74d1a3a392bf1aaaf5c2dcc8273daf66 Any thoughts are appreciated, I've already read "Laptop suggestions?" by Frank Mayhar-2 regards -Jakub Lach -- View this message in context: http://www.nabble.com/7-STABLE-on-Fujitsu-Siemens-E8420-E8410--Lenovo-T61-tp19639964p19639964.html Sent from the freebsd-mobile mailing list archive at Nabble.com. From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 00:16:46 2008 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 086C41065686 for ; Thu, 25 Sep 2008 00:16:46 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id D171D8FC1C for ; Thu, 25 Sep 2008 00:16:45 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KieXE-0002LL-LA for freebsd-mobile@freebsd.org; Wed, 24 Sep 2008 17:16:44 -0700 Message-ID: <19660745.post@talk.nabble.com> Date: Wed, 24 Sep 2008 17:16:44 -0700 (PDT) From: Jakub Lach To: freebsd-mobile@freebsd.org In-Reply-To: <48C41BD1.6070903@csub.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jakub_lach@mailplus.pl References: <48C41BD1.6070903@csub.edu> Subject: Re: ThinkPad T400 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, 25 Sep 2008 00:16:46 -0000 Russell Jackson-3 wrote: > > I received my t400 at last, and I thought I'd share my experiences with > it so far. > > ----8<-----snip--- > > Any progress with FreeBSD? It would be nice to have Montevina FreeBSD laptop. /I'm looking for a notebook that would have: nice finish like T Thinkpads, Intel integrated graphicscard, running 7 STABLE amd64, 4GB DDR3, Fast Penryn, working sound and wifi/ regards -Jakub Lach -- View this message in context: http://www.nabble.com/ThinkPad-T400-tp19361215p19660745.html Sent from the freebsd-mobile mailing list archive at Nabble.com. From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 04:45:49 2008 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 561FC1065686 for ; Thu, 25 Sep 2008 04:45:49 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id 31BC18FC19 for ; Thu, 25 Sep 2008 04:45:49 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe33:7e9a]) by tinker.exit.com (8.14.2/8.14.2) with ESMTP id m8P4hxsv014211 for ; Wed, 24 Sep 2008 21:43:59 -0700 (PDT) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1222317839; bh=oYg9VaeyjorAfi/ruIitgMHRamOp12a5DWQ/YFj2hQc=; h=Subject:From:Reply-To:To:Content-Type:Content-Transfer-Encoding: Date:Message-Id:Mime-Version; b=B6Y+Nn8nwsCaWNUoBl33g7begU7wmZFRqk b6j2QZUUCBX/iFa18Dvx1AuiV6qPglkV/mJyWvbtRA8znlR77isIyjF+0YDwBZbM9Qj a915trNENIdLMwym5i/qQePqy0FVszDR2uBQJjUGXr20XfQU2OdD7/cu876Uxdr/Bp7 6W8= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.2/8.14.2) with ESMTP id m8P4jmiw001864 for ; Wed, 24 Sep 2008 21:45:48 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.2/8.14.2/Submit) id m8P4jmlB001863 for freebsd-mobile@freebsd.org; Wed, 24 Sep 2008 21:45:48 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: freebsd-mobile Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Wed, 24 Sep 2008 21:45:48 -0700 Message-Id: <1222317948.1740.10.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.93.3/8327/Wed Sep 24 17:30:26 2008 on tinker.exit.com X-Virus-Status: Clean Subject: Atheros wireless problems. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 04:45:49 -0000 So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I believe) Atheros chipset in it; it's an a/b/g card. This is to use while the chipset embedded in my laptop isn't supported. It came today, I installed it tonight and, well, problems. I can get it to associate and, sometimes, even to get an IP address, but as soon as I start trying to actually pass traffic on it, all hell breaks loose. It starts timing out and the ath_hal starts complaining. Essential information: ath0@pci0:57:0:0: class=0x020000 card=0x3a631186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet ath0: flags=8843 metric 0 mtu 2290 ether 00:13:46:11:6b:41 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:13:46:11:6b:41 inet6 fe80::213:46ff:fe11:6b41%wlan0 prefixlen 64 scopeid 0x4 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid Unwired channel 1 (2412 Mhz 11g) bssid 00:1f:33:82:2f:6d regdomain FCC indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 18 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst ff roaming MANUAL >From the dmesg: ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: mac 5.9 phy 4.3 radio 3.6 wlan0: Ethernet address: 00:13:46:11:6b:41 Then from /var/log/messages: Sep 24 21:14:11 kernel: ath0: device timeout Sep 24 21:14:11 kernel: ath0: ath_reset: unable to reset hardware; hal status 3230480741 I've also seen: Sep 24 21:03:55 auton kernel: ath0: unable to reset hardware; hal status 3310983360 Sep 24 21:02:35 auton kernel: ath0: unable to reset hardware; hal status 0 But it has only been those messages. I haven't yet tried turning on bootverbose but I can if you would like. Any ideas? Any suggestions? As I sit here (using the wired em0 instead of ath0) the lights on the card are happily blinking but it's not doing anything at all. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 13:25:43 2008 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 9247A1065698 for ; Thu, 25 Sep 2008 13:25:43 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 670E78FC0A for ; Thu, 25 Sep 2008 13:25:43 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so379451rvf.43 for ; Thu, 25 Sep 2008 06:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8u87BSdVLwKsQlbIHJL94WY99W1wpYmV5sjEN2SqfZc=; b=QMnMh6Mk4agqT/dERbsN7KotNhpJVByl3MLmFGAz3gV4/E+aGDiBPOgLMRQBCN28j0 4Xq25shep8IBM6LQGxPaGDlMjkNwuSZKDNozy+Z4rfrFAvsPX9lgXYDTsVW+EGCJHzhF EZrf7wQgkEz6EcYQoh85hOxX8SFS092TGF3Yo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=LOTySpAWsEi9yZI10T1jgE66xUWhoaQYxFyRk/Y9za2hwY1YiW9JBLdiLFDUNEUQIL 4jlw04ho/MbVsl+mGvTM37SqOy3RPXgEAfyXBmP1vp/Y4EpuKnzD83gGlMUgkGSB+LpG 4r5WStYJgkl3NJMsdVJpzh7JS8XeZGYjeoDqk= Received: by 10.141.29.18 with SMTP id g18mr4099956rvj.162.1222347582862; Thu, 25 Sep 2008 05:59:42 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Thu, 25 Sep 2008 05:59:42 -0700 (PDT) Message-ID: <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> Date: Thu, 25 Sep 2008 14:59:42 +0200 From: "Paul B. Mahol" To: frank@exit.com In-Reply-To: <1222317948.1740.10.camel@jill.exit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1222317948.1740.10.camel@jill.exit.com> Cc: freebsd-mobile Subject: Re: Atheros wireless problems. 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, 25 Sep 2008 13:25:43 -0000 On 9/25/08, Frank Mayhar wrote: > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > believe) Atheros chipset in it; it's an a/b/g card. This is to use > while the chipset embedded in my laptop isn't supported. It came today, > I installed it tonight and, well, problems. > > I can get it to associate and, sometimes, even to get an IP address, but > as soon as I start trying to actually pass traffic on it, all hell > breaks loose. It starts timing out and the ath_hal starts complaining. What version of ath_hal are you using? Try one from CURRENT. From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 13:38:03 2008 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 75720106568D for ; Thu, 25 Sep 2008 13:38:03 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id 306A38FC13 for ; Thu, 25 Sep 2008 13:38:03 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe33:7e9a]) by tinker.exit.com (8.14.2/8.14.2) with ESMTP id m8PDa5d0020579; Thu, 25 Sep 2008 06:36:05 -0700 (PDT) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1222349765; bh=LzQC/Uqe5uEN8pBMKS8KHjmWIL/Z2mcKFsueaTHov5Y=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type: Content-Transfer-Encoding:Date:Message-Id:Mime-Version; b=tHZsActi FihfV/ZLTheqhlkQemVzQcoUU+73F4un8DXHNLjSrDMw5CJ65DxcB9XwsujhTRTA7sf QjeSF57cNnCzDHxbe9lWAgoMs5VOMxn06+/7oh28K7LBBKRtUNt2r+MdvVD5mxNsPwK q7FzTwXDjXQbXqhn11KrTtEP78/fo= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.2/8.14.2) with ESMTP id m8PDc2Qx005052; Thu, 25 Sep 2008 06:38:02 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.2/8.14.2/Submit) id m8PDc1jq005051; Thu, 25 Sep 2008 06:38:01 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: "Paul B. Mahol" In-Reply-To: <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> References: <1222317948.1740.10.camel@jill.exit.com> <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Thu, 25 Sep 2008 06:38:01 -0700 Message-Id: <1222349881.1740.13.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.93.3/8330/Thu Sep 25 04:58:22 2008 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-mobile Subject: Re: Atheros wireless problems. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 13:38:03 -0000 On Thu, 2008-09-25 at 14:59 +0200, Paul B. Mahol wrote: > On 9/25/08, Frank Mayhar wrote: > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > > believe) Atheros chipset in it; it's an a/b/g card. This is to use > > while the chipset embedded in my laptop isn't supported. It came today, > > I installed it tonight and, well, problems. > > > > I can get it to associate and, sometimes, even to get an IP address, but > > as soon as I start trying to actually pass traffic on it, all hell > > breaks loose. It starts timing out and the ath_hal starts complaining. > > What version of ath_hal are you using? Try one from CURRENT. Sorry, I forgot to mention that I am actually running 8-current: ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 14:41:31 2008 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 E1EC610656D7 for ; Thu, 25 Sep 2008 14:41:31 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id B5B518FC8E for ; Thu, 25 Sep 2008 14:41:31 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so405532rvf.43 for ; Thu, 25 Sep 2008 07:41:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=x1Ll6d91K43JHKmNIuYy2hw/e7YtVUInOPCcuH2IpGw=; b=g8cc9qoCUB/U/W+NRI7J91YFsY8I6LPNnlsOO1pSJIl9W0IdWoAnhmMtI1nVk0I5sj oAVzweK+NzeQyWl5rm0KPwDJH/TAbNafWRjgI6VdPARqNcvvJgfDFL851C+DVMKsYmyi OqIKQcGd+vh8dW7WJn7kaH5bV0X2lRbofRr5c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=rShiiTG+l+whRf46TzjYvA+o+oNIWRC4zFF4zOCRARKKjEdnKT0BxJP49rrSnVmk3/ 4WmMYUa7/lSZ3MoJ2NweAB/IUTbRzQbf9nYFBcunD5BTAuZrfwrxhjAqRjpudpngyeGV 5DqmFPwJkJQZiAHutgb1DqE6sksu/vHsn14rU= Received: by 10.141.37.8 with SMTP id p8mr4141325rvj.256.1222353690505; Thu, 25 Sep 2008 07:41:30 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Thu, 25 Sep 2008 07:41:30 -0700 (PDT) Message-ID: <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> Date: Thu, 25 Sep 2008 16:41:30 +0200 From: "Paul B. Mahol" To: "John Hay" In-Reply-To: <20080922132500.GA25677@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 25 Sep 2008 14:41:32 -0000 On 9/22/08, John Hay wrote: > Hi > > I'm trying out the new ath/wlan stuff in current. Should one still be > able to set the bssid in adhoc mode? We normally lock the bssid in > an adhoc network because of problems that the network split and does > not merge, if you do not do it. > > What I have done is this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > # ifconfig wlan0 ssid ptamesh up > > Up to here works well. It will scan and if it finds another node with the > same ssid, it will "lock" on that channel and use the correct bssid. > > If it does not find another node with the same ssid, it will start it > own thing on channel 10. But it looks like one cannot set the bssid. > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > ifconfig: 02:07:ca:fe:ba:be: bad value I had similar experience with STA mode, instead I use ap (ap is alias for bssid, at least it works in STA mode) I never bothered is this bug in manual page, ifconfig or in something else ... From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 15:53:33 2008 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 4BEF81065688 for ; Thu, 25 Sep 2008 15:53:33 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0089B8FC23 for ; Thu, 25 Sep 2008 15:53:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8PFrJkR084643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Sep 2008 08:53:19 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DBB3EF.3060909@freebsd.org> Date: Thu, 25 Sep 2008 08:53:19 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: frank@exit.com References: <1222317948.1740.10.camel@jill.exit.com> In-Reply-To: <1222317948.1740.10.camel@jill.exit.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile Subject: Re: Atheros wireless problems. 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, 25 Sep 2008 15:53:33 -0000 Frank Mayhar wrote: > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > believe) Atheros chipset in it; it's an a/b/g card. This is to use > while the chipset embedded in my laptop isn't supported. It came today, > I installed it tonight and, well, problems. > > I can get it to associate and, sometimes, even to get an IP address, but > as soon as I start trying to actually pass traffic on it, all hell > breaks loose. It starts timing out and the ath_hal starts complaining. > > Essential information: > > ath0@pci0:57:0:0: class=0x020000 card=0x3a631186 chip=0x0013168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet > ath0: flags=8843 metric 0 mtu 2290 > ether 00:13:46:11:6b:41 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:13:46:11:6b:41 > inet6 fe80::213:46ff:fe11:6b41%wlan0 prefixlen 64 scopeid 0x4 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid Unwired channel 1 (2412 Mhz 11g) bssid 00:1f:33:82:2f:6d > regdomain FCC indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF TKIP 2:128-bit txpower 18 bmiss 7 scanvalid 450 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS > wme burst ff roaming MANUAL > > >From the dmesg: > ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 5.9 phy 4.3 radio 3.6 > wlan0: Ethernet address: 00:13:46:11:6b:41 > > Then from /var/log/messages: > Sep 24 21:14:11 kernel: ath0: device timeout > Sep 24 21:14:11 kernel: ath0: ath_reset: unable to reset hardware; hal status 3230480741 > > I've also seen: > Sep 24 21:03:55 auton kernel: ath0: unable to reset hardware; hal status 3310983360 > Sep 24 21:02:35 auton kernel: ath0: unable to reset hardware; hal status 0 > > But it has only been those messages. I haven't yet tried turning on > bootverbose but I can if you would like. > > Any ideas? Any suggestions? As I sit here (using the wired em0 instead > of ath0) the lights on the card are happily blinking but it's not doing > anything at all. > The status codes look bogus. In 0.10.5.10 there is a code path through reset where status is not set if the chip is not brought out of low power mode. Why this might happen is beyond me (could be a cardbus problem) but if you initialize status to a known value before the hal calls that are failing this might confirm that as the problem. I've fixed the hal fwiw. Sam From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 16:13:42 2008 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 2B7F41065688 for ; Thu, 25 Sep 2008 16:13:42 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 677DB8FC19 for ; Thu, 25 Sep 2008 16:13:41 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 6368633CD1; Thu, 25 Sep 2008 18:13:38 +0200 (SAST) Date: Thu, 25 Sep 2008 18:13:38 +0200 From: John Hay To: "Paul B. Mahol" Message-ID: <20080925161338.GA69284@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 25 Sep 2008 16:13:42 -0000 On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: > On 9/22/08, John Hay wrote: > > Hi > > > > I'm trying out the new ath/wlan stuff in current. Should one still be > > able to set the bssid in adhoc mode? We normally lock the bssid in > > an adhoc network because of problems that the network split and does > > not merge, if you do not do it. > > > > What I have done is this: > > > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > # ifconfig wlan0 ssid ptamesh up > > > > Up to here works well. It will scan and if it finds another node with the > > same ssid, it will "lock" on that channel and use the correct bssid. > > > > If it does not find another node with the same ssid, it will start it > > own thing on channel 10. But it looks like one cannot set the bssid. > > > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > > ifconfig: 02:07:ca:fe:ba:be: bad value > > I had similar experience with STA mode, instead I use ap (ap is alias > for bssid, at least it works in STA mode) > I never bothered is this bug in manual page, ifconfig or in something else ... Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. Just do not try to unset it with "ifconfig wlan0 ap -". That is an alias for "panic now" :-) So it looks like ifconfig is getting confused with the many different uses of the keyword bssid. I must say I still do not understand what the other use for bssid is. Close to the end of ifconfig/ifieee80211.c there are these: DEF_CMD_ARG("bssid", set80211bssid), DEF_CMD_ARG("ap", set80211bssid), ... DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), So my guess is that I was hitting the clone version when in fact I needed the other version. Luckily ap does not have a clone version. So when should the clone version be used? And how does ifconfig decide which one to use? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 17:50:55 2008 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 88E62106568C for ; Thu, 25 Sep 2008 17:50:55 +0000 (UTC) (envelope-from raj@csub.edu) Received: from mh1.csub.edu (mh1.csub.edu [136.168.1.95]) by mx1.freebsd.org (Postfix) with ESMTP id 70F708FC17 for ; Thu, 25 Sep 2008 17:50:55 +0000 (UTC) (envelope-from raj@csub.edu) Received: from strider.csub.edu (strider.csub.edu [136.168.65.65]) by mh1.csub.edu (8.13.8/8.13.8) with ESMTP id m8PHosKR055966; Thu, 25 Sep 2008 10:50:54 -0700 (PDT) (envelope-from raj@csub.edu) Message-ID: <48DBCF7E.9080005@csub.edu> Date: Thu, 25 Sep 2008 10:50:54 -0700 From: Russell Jackson User-Agent: Thunderbird 2.0.0.14 (X11/20080703) MIME-Version: 1.0 To: Jakub Lach References: <48C41BD1.6070903@csub.edu> <19660745.post@talk.nabble.com> In-Reply-To: <19660745.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: ThinkPad T400 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, 25 Sep 2008 17:50:55 -0000 Jakub Lach wrote: > > Russell Jackson-3 wrote: >> I received my t400 at last, and I thought I'd share my experiences with >> it so far. >> >> ----8<-----snip--- >> >> > > Any progress with FreeBSD? It would be nice to have Montevina FreeBSD > laptop. > > > /I'm looking for a notebook that would have: nice finish like T Thinkpads, > Intel integrated graphicscard, running 7 STABLE amd64, 4GB DDR3, Fast > Penryn, working sound and wifi/ > I noticed there was a new September CURRENT snapshot, but I haven't had time to try it. The other problem is that Ubuntu has been working too well which makes me hesitant to start all over from scratch ;-). -- Russell A. Jackson Network Analyst California State University, Bakersfield Confidence is the feeling you have before you understand the situation. From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 18:59:38 2008 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 131071065690 for ; Thu, 25 Sep 2008 18:59:38 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id D87AD8FC1E for ; Thu, 25 Sep 2008 18:59:37 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so491565rvf.43 for ; Thu, 25 Sep 2008 11:59:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=KgaXvdKmrgrzO0E4RnYvLlbwPK8ksPnmOK2KzKskMS8=; b=Q+yTvqWIDVqlyEVFF3yr0x79lX7om25Vb90ftdwKHk0HN1AUC6cqfgWrQB0AqcxmUh 490+6NqCGDCFgINzBQLujBmy5MWEia3LrewmEoLrPcLoDD7qpRB0cvsQwgzFHM4EYMXn BabZY5yTzUAAk4i+Ycat1hUpgZRJGsaiAOCm4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=vIk1SuiGoJ76+bGG3WBdvMDGqzT2Zz94xG3lh1UI7mRDigU+nmY3KoXMOI9gZv/fOU dywF82RXCAP9K7qo/+avXfgfF8RUXa3P8fNYlKZXCUL+eLU1W40zpybZlfJTBZTpijEL GtGeHx0OrLbUm8QolO3RBep/s+KiITcZ13U4M= Received: by 10.141.52.5 with SMTP id e5mr71320rvk.125.1222369177455; Thu, 25 Sep 2008 11:59:37 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Thu, 25 Sep 2008 11:59:37 -0700 (PDT) Message-ID: <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> Date: Thu, 25 Sep 2008 20:59:37 +0200 From: "Paul B. Mahol" To: "John Hay" In-Reply-To: <20080925161338.GA69284@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 25 Sep 2008 18:59:38 -0000 On 9/25/08, John Hay wrote: > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >> On 9/22/08, John Hay wrote: >> > Hi >> > >> > I'm trying out the new ath/wlan stuff in current. Should one still be >> > able to set the bssid in adhoc mode? We normally lock the bssid in >> > an adhoc network because of problems that the network split and does >> > not merge, if you do not do it. >> > >> > What I have done is this: >> > >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >> > # ifconfig wlan0 ssid ptamesh up >> > >> > Up to here works well. It will scan and if it finds another node with >> > the >> > same ssid, it will "lock" on that channel and use the correct bssid. >> > >> > If it does not find another node with the same ssid, it will start it >> > own thing on channel 10. But it looks like one cannot set the bssid. >> > >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >> > ifconfig: 02:07:ca:fe:ba:be: bad value >> >> I had similar experience with STA mode, instead I use ap (ap is alias >> for bssid, at least it works in STA mode) >> I never bothered is this bug in manual page, ifconfig or in something else >> ... > > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > Just do not try to unset it with "ifconfig wlan0 ap -". That is an > alias for "panic now" :-) Well, on my system it doesnt panic here. So more info to debug "your" panic is required ... > > So it looks like ifconfig is getting confused with the many different > uses of the keyword bssid. > > I must say I still do not understand what the other use for bssid is. > Close to the end of ifconfig/ifieee80211.c there are these: > > DEF_CMD_ARG("bssid", set80211bssid), > DEF_CMD_ARG("ap", set80211bssid), > ... > DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > > So my guess is that I was hitting the clone version when in fact I > needed the other version. Luckily ap does not have a clone version. > So when should the clone version be used? And how does ifconfig > decide which one to use? From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 05:55:25 2008 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 0AC76106568B for ; Fri, 26 Sep 2008 05:55:25 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 305888FC23 for ; Fri, 26 Sep 2008 05:55:24 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 51EBE33CD9; Fri, 26 Sep 2008 07:55:22 +0200 (SAST) Date: Fri, 26 Sep 2008 07:55:22 +0200 From: John Hay To: "Paul B. Mahol" Message-ID: <20080926055522.GA13842@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Fri, 26 Sep 2008 05:55:25 -0000 On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: > On 9/25/08, John Hay wrote: > > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: > >> On 9/22/08, John Hay wrote: > >> > Hi > >> > > >> > I'm trying out the new ath/wlan stuff in current. Should one still be > >> > able to set the bssid in adhoc mode? We normally lock the bssid in > >> > an adhoc network because of problems that the network split and does > >> > not merge, if you do not do it. > >> > > >> > What I have done is this: > >> > > >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > >> > # ifconfig wlan0 ssid ptamesh up > >> > > >> > Up to here works well. It will scan and if it finds another node with > >> > the > >> > same ssid, it will "lock" on that channel and use the correct bssid. > >> > > >> > If it does not find another node with the same ssid, it will start it > >> > own thing on channel 10. But it looks like one cannot set the bssid. > >> > > >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > >> > ifconfig: 02:07:ca:fe:ba:be: bad value > >> > >> I had similar experience with STA mode, instead I use ap (ap is alias > >> for bssid, at least it works in STA mode) > >> I never bothered is this bug in manual page, ifconfig or in something else > >> ... > > > > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > > Just do not try to unset it with "ifconfig wlan0 ap -". That is an > > alias for "panic now" :-) > Well, on my system it doesnt panic here. > So more info to debug "your" panic is required ... I'll have to see if I can reproduce it. > > So it looks like ifconfig is getting confused with the many different > > uses of the keyword bssid. > > > > I must say I still do not understand what the other use for bssid is. > > Close to the end of ifconfig/ifieee80211.c there are these: > > > > DEF_CMD_ARG("bssid", set80211bssid), > > DEF_CMD_ARG("ap", set80211bssid), > > ... > > DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > > DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > > > > So my guess is that I was hitting the clone version when in fact I > > needed the other version. Luckily ap does not have a clone version. > > So when should the clone version be used? And how does ifconfig > > decide which one to use? I looked into the ifconfig code a bit more. I think that with the current code in the ifconfig() and cmd_lookup() functions, it is imposssible to have two different keywords that share the same keyword. cmd_lookup() will always search until it finds the first instance in the list and return that. The first instance in this case being the last one added. So either the code must change or one of the bssid keywords have to change. My suggestion would be to keep the bssid for which ap is an alias and change the other one. Anybody have a suggestion of what to change it to? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 06:29:54 2008 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 BC3A61065686 for ; Fri, 26 Sep 2008 06:29:54 +0000 (UTC) (envelope-from waynehendricks@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 8CE768FC21 for ; Fri, 26 Sep 2008 06:29:54 +0000 (UTC) (envelope-from waynehendricks@gmail.com) Received: by wa-out-1112.google.com with SMTP id n4so424481wag.27 for ; Thu, 25 Sep 2008 23:29:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=xKoR4YcF/6UF8XPKXUya8WHvHgyChbJ+UiWZcTVspcE=; b=WyAjpstmT3DQPYDH8xLEo/QsIAMqPoGAnWff9OBixZwZMJtbLIpQnul+j7Fmox86Yy 6RUOOPIVJ3/ZuSmWOcr68a+li7RRL51QHomW2v5eFFFpwXiA2VueiQ2pgvw0FLPFIzUQ XaIwWEMSlYq5bjA7TeMOhBtB5A7MskNNCI8rg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=XqvYotognk9ypcyHyYErxh777aUHjD5bEM6FiePiJk8Ouktj6yNTqtMnYPmweZmfAt +EhFhW/X1M6M1KMJ8HoX/4mYlrCuJW7QJuvTluVS35HKxeCRJx65f4KtXR5B+H1gJlcj WXdMSzfO8YwcK7+fmdE9EbosoDZflpVkb5D6w= Received: by 10.114.178.13 with SMTP id a13mr819943waf.182.1222408930309; Thu, 25 Sep 2008 23:02:10 -0700 (PDT) Received: by 10.114.190.16 with HTTP; Thu, 25 Sep 2008 23:02:10 -0700 (PDT) Message-ID: <3b965dec0809252302j2534db24j1666626f3340090d@mail.gmail.com> Date: Fri, 26 Sep 2008 01:02:10 -0500 From: "Wayne Hendricks" To: freebsd-mobile@freebsd.org In-Reply-To: <3b965dec0809252258t15722eecn29494431bced3061@mail.gmail.com> MIME-Version: 1.0 References: <3b965dec0809252258t15722eecn29494431bced3061@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Hostapd network issue 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: Fri, 26 Sep 2008 06:29:54 -0000 I have been trying to make hostapd work with the wifi card in my gateway box. WPA stays working for only a short time before hostapd locks up and needs to be restarted. I believe the hosapd config is fine, shows no errors. Running 7.0-RELEASE-p4 amd64 with mini-pci Atheros 5212 chipset. ath0 and bge1 are bridged to bridge0. I have included the hostapd debug output below. What is this ioctl[SIOCS80211] weirdness? Configuration file: /etc/hostapd.conf ctrl_interface_group=0 (from group name 'wheel') bsd_set_iface_flags: dev_up=0 BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits) ath0: IEEE 802.11 Fetching hardware channel/rate support not supported. Flushing old station entries bsd_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3 Deauthenticate all stations bsd_set_privacy: enabled=0 Mode: IEEE 802.11g Channel: 11 Frequency: 0 MHz bsd_del_key: addr=00:00:00:00:00:00 key_idx=0 bsd_del_key: addr=00:00:00:00:00:00 key_idx=1 bsd_del_key: addr=00:00:00:00:00:00 key_idx=2 bsd_del_key: addr=00:00:00:00:00:00 key_idx=3 bsd_get_ssid: ssid="bsdap" Using interface ath0 with hwaddr 00:90:96:6b:0f:c6 and ssid 'bsdap' SSID - hexdump_ascii(len=9): 52 4e 73 65 63 75 72 65 47 bsdap PSK (ASCII passphrase) - hexdump_ascii(len=12): 65 74 68 65 72 61 70 65 31 31 31 36 mypassphrase PSK (from passphrase) - hexdump(len=32): 17 ae 54 6a a7 c4 fc ce e2 d4 2e 07 0d 08 09 56 41 d3 a4 6a d2 18 26 d1 36 22 56 fe a0 af 26 43 bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: group key cipher=TKIP (1) bsd_configure_wpa: pairwise key ciphers=0xa bsd_configure_wpa: key management algorithms=0x2 bsd_configure_wpa: rsn capabilities=0x0 bsd_configure_wpa: enable WPA= 0x1 bsd_set_iface_flags: dev_up=1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 bsd_set_privacy: enabled=1 ath0: Setup of interface done. ath0: STA 00:1e:c2:bf:74:60 IEEE 802.11: associated New STA ath0: STA 00:1e:c2:bf:74:60 WPA: event 1 notification bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 ath0: STA 00:1e:c2:bf:74:60 WPA: start authentication WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=0 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: unauthorizing port WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state AUTHENTICATION WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state AUTHENTICATION2 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITPSK WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKSTART ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 9f 2b fa 4e 6e 00 d2 a0 fd 9e f0 c1 fd be 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 1e c2 bf 74 60 00 00 96 6b 0f c6 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd be 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cf 86 6a 87 74 59 72 dc 2f 01 f9 8b b4 20 51 1f 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=1 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:1e:c2:bf:74:60 ath0: STA 00:1e:c2:bf:74:60 WPA: pairwise key handshake completed (WPA) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 3b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 d8 ba b9 34 15 fd ae 04 7c 59 05 d4 08 70 4c 00 28 36 25 48 ae 3c 8 d ad 9b 27 20 45 68 36 d7 57 ba 57 49 0f 7d e9 2b 1d 6b b5 21 c1 a4 e5 77 fc 57 fd 57 c1 90 be a2 50 a4 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 46 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 04 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 3a d0 8a fd 74 2d 9a cf ba eb 75 56 26 71 63 00 28 36 25 48 ae 3c 8 d ad 9b 27 20 45 68 36 d7 57 ba 57 49 0f 7d e9 2b 1d 6b b5 21 c1 a4 e5 77 fc 37 fd 57 c1 00 be a2 50 a4 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: associated New STA ath0: STA 00:21:e9:6e:98:d0 WPA: event 1 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 ath0: STA 00:21:e9:6e:98:d0 WPA: start authentication WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITPSK WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKSTART ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 21 e9 6e 68 d0 00 90 96 6b 0f c6 58 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bf 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 21 e9 6e 98 d0 00 90 96 6b 0f c5 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bf 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e2 55 c7 5a e3 2d 7a 54 f2 6d f0 7b 9f cc ca b3 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=1 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:21:e9:6e:98:d0 ath0: STA 00:21:e9:6e:98:d0 WPA: pairwise key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 98 d0 00 90 96 6b 0f c6 68 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bb 76 69 1b 31 76 d5 81 87 d1 fb f5 ac 85 f1 d7 00 28 f6 9f 0d ca 6e 4 b 9c 54 56 98 09 75 79 a1 35 b0 90 a2 77 33 48 3e 5c 5d 03 cc 8e 6b 1c 10 cd af a5 66 58 5f d2 fb 3d 48 ath0: STA 00:21:e9:6e:98:d0 WPA: EAPOL-Key timeout WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 98 d0 00 90 96 6b 0f c6 88 8e 02 03 00 47 fe 03 92 00 20 00 00 00 00 00 00 00 04 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ec 85 4f 9e d0 f7 89 9c a5 aa da f7 94 32 96 1b 00 28 f6 9f 0d ca 6e 4 b 9c 54 56 98 09 75 79 a1 35 b0 90 a2 77 33 48 3e 5c 5d 03 cc 3e 6b 1c 10 cd af a5 96 58 5f d2 fb 3d 48 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:21:e9:6e:98:d0 WPA: group key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: deassociated ath0: STA 00:21:e9:6e:98:d0 WPA: event 2 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state DISCONNECTED WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port Could not set station 00:21:e9:6e:98:d0 flags for kernel driver (errno=22). ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=2 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 3b 0f c6 88 8e 02 03 00 87 fe 03 a2 00 20 00 00 00 00 00 00 00 05 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 21 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2e 4a 9b 73 a4 2a 85 58 43 ea 4b 26 39 52 da 0b 00 28 97 d8 b5 38 1a 9 9 dc 43 65 b5 bd ac 8c 7e 35 2c 12 7c 55 d4 79 0a 54 68 4c 5c 59 36 5b f6 69 31 ad 4a 90 ff 81 be c6 4f IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 76 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 06 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 16 82 a2 6d 95 4d 6b 3c ce 5b 05 47 76 55 00 28 7a a2 9a 85 ef a f a9 be 86 56 94 45 a3 ab b8 a5 b3 d5 44 3b a4 d3 9f 7b 3d ea 97 e6 c3 ed 9e 42 da 4b 91 2d fd 7f 1e 8d IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: associated New STA ath0: STA 00:21:e9:6e:98:d0 WPA: event 1 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 ath0: STA 00:21:e9:6e:98:d0 WPA: start authentication WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITPSK WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKSTART ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 21 e9 6e 98 d0 00 30 96 6b 0f c6 88 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 3b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 21 e9 6e 78 d0 00 90 96 6b 0f c6 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 19 95 a0 4e 64 c6 43 6c e9 8c 02 ef 75 27 f9 e5 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 40 f2 02 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=1 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:21:e9:6e:98:d0 ath0: STA 00:21:e9:6e:98:d0 WPA: pairwise key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 08 d0 00 90 96 6b 0f c6 88 5e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50 dc 19 fc 24 e2 56 37 16 14 5a 0b 00 25 c2 47 00 28 78 92 48 df 3b e f 3c d7 25 82 34 d2 32 7d 1f cc 12 d1 4e c0 89 dc 29 80 88 45 95 27 13 49 b0 da ef f9 c9 fd f0 52 a9 b5 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:21:e9:6e:98:d0 WPA: group key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: deassociated ath0: STA 00:21:e9:6e:98:d0 WPA: event 2 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state DISCONNECTED WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port Could not set station 00:21:e9:6e:98:d0 flags for kernel driver (errno=22). Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=2 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 78 8e 02 03 00 87 fe 03 a2 00 20 00 00 00 00 00 00 00 07 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 00 be eb 48 36 b5 ad 1f 17 bc 64 ca 6b c8 ca 00 28 8a 2b 24 9f ee 4 4 0f e7 4a ad a8 55 62 cd b9 d0 69 cc af e4 94 01 aa d8 e9 cf cc a7 ed 6e e0 90 b5 3c 35 1a ae 2e 32 d7 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 40 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 08 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c1 50 c3 fa 32 83 f8 05 c4 c3 78 e5 cf 48 25 79 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 97 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 10 00 00 00 00 00 00 00 09 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 b1 39 72 aa d0 25 02 a4 5b 01 55 a9 c6 5b cf 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 98 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 0a 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 79 9c 20 34 dd 26 28 c7 c2 6f a3 1c a4 03 44 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 02 00 20 00 00 00 00 00 00 00 0b 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 91 86 ea b0 4b 7f c5 2b 2c 9c b2 94 67 d4 e6 14 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a8 d7 73 20 6d f1 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state KEYERROR WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state DISCONNECT hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:1e:c2:bf:74:60 reason 2 bsd_sta_deauth: addr=00:1e:c2:bf:74:60 reason_code=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state DISCONNECTED WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=0 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: unauthorizing port Could not set station 00:1e:c2:bf:74:60 flags for kernel driver (errno=22). ath0: STA 00:1e:c2:bf:74:60 IEEE 802.11: deauthenticated due to local deauth request GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument Signal 2 received - terminating Flushing old station entries bsd_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3 Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_ieee8021x: enabled=0 bsd_set_iface_flags: dev_up=0 From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 14:20:56 2008 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 2C9961065686 for ; Fri, 26 Sep 2008 14:20:56 +0000 (UTC) (envelope-from johnseth_2007@yahoo.com) Received: from n65a.bullet.mail.sp1.yahoo.com (n65a.bullet.mail.sp1.yahoo.com [98.136.45.12]) by mx1.freebsd.org (Postfix) with SMTP id 0D8168FC12 for ; Fri, 26 Sep 2008 14:20:56 +0000 (UTC) (envelope-from johnseth_2007@yahoo.com) Received: from [216.252.122.218] by n65.bullet.mail.sp1.yahoo.com with NNFMP; 26 Sep 2008 14:08:25 -0000 Received: from [69.147.65.162] by t3.bullet.sp1.yahoo.com with NNFMP; 26 Sep 2008 14:08:25 -0000 Received: from [127.0.0.1] by omp407.mail.sp1.yahoo.com with NNFMP; 26 Sep 2008 14:08:25 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 126795.87552.bm@omp407.mail.sp1.yahoo.com Received: (qmail 56314 invoked by uid 60001); 26 Sep 2008 14:08:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=deGrLVWUG2o3pIVPO7Dh4/ycsmsdIRYxoDbR48JezlIwJiy727I/9uBYbx7AMk6Z+HJZzXYCSgZ2em8QDpNZBksHCJwrhzRUyJmf9Cx2SKWA35uwDSXNqUn20Fit3AmrhKYbuVX1RLst2ZdxQ6mX91hRXCinkG0M8UX/mTLg5+U=; X-YMail-OSG: W7NiGgUVM1nEz1P5QELDLSm8CwucX4RmyaFWwuXcq5xkcxXPT4SLQ80nVzGzZDBoaY4QYCA9Up7LA7Ggpif5jKry3CSlu21cqpZOpd5PlFF70RlVCJLjQ7TF331KaEGb3qLeJQ-- Received: from [123.201.116.181] by web45203.mail.sp1.yahoo.com via HTTP; Fri, 26 Sep 2008 07:08:23 PDT X-Mailer: YahooMailWebService/0.7.218.2 Date: Fri, 26 Sep 2008 07:08:23 -0700 (PDT) From: john seth To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Message-ID: <688762.55289.qm@web45203.mail.sp1.yahoo.com> X-Mailman-Approved-At: Fri, 26 Sep 2008 16:05:24 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: facility for mobile DDR RAM X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: johnseth_2007@yahoo.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2008 14:20:56 -0000 Hi friends, =A0=A0=A0=A0 I want to know whether there is facility for mobile DDR RAM, so that we can switch of a bank(s) without loosing the data in other bank(s). Thanks.=0A=0A=0A From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 17:12:15 2008 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 9C6721065697 for ; Fri, 26 Sep 2008 17:12:15 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0BA8FC16 for ; Fri, 26 Sep 2008 17:12:15 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so951103rvf.43 for ; Fri, 26 Sep 2008 10:12:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=/E/REZyzOxsidkZNYxnjUbQJun+qXSiisN0QVdzAkR4=; b=Jw1QopYONH36zHzPnVi4oBCadbrrKZtvX8KqgsV83oIaFxDs8STrBLbKpyFGnMvIr6 mzEYDVYDCfMeVIjmVt8s4tjA3QjR1UrfzJqEd8kQlFEtCOAy0BtTMLiX3V25eRfk+tHw OV9n25Pw+qOSo6nh+1L6g3YHh031T1wJt48SA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xF1f06fi/dq58DDxlL1LsRYzFUF3DT3fIRuA0KTjeBgMRJyxw0L8oOnNH/VNyCKLag aSgvERz5Y3M1GRuEjpT8GVBopf8bptEErcRQLfnRfQM0DrH3dQAUCNNpzU6Cp7C7pCnF GsDclbGMjLO3Mo8JCSwYM3I1Z1+t0BIliKJ4g= Received: by 10.141.169.11 with SMTP id w11mr842981rvo.63.1222449135061; Fri, 26 Sep 2008 10:12:15 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Fri, 26 Sep 2008 10:12:15 -0700 (PDT) Message-ID: <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> Date: Fri, 26 Sep 2008 19:12:15 +0200 From: "Paul B. Mahol" To: "John Hay" In-Reply-To: <20080926055522.GA13842@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Fri, 26 Sep 2008 17:12:15 -0000 On 9/26/08, John Hay wrote: > On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >> On 9/25/08, John Hay wrote: >> > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >> >> On 9/22/08, John Hay wrote: >> >> > Hi >> >> > >> >> > I'm trying out the new ath/wlan stuff in current. Should one still be >> >> > able to set the bssid in adhoc mode? We normally lock the bssid in >> >> > an adhoc network because of problems that the network split and does >> >> > not merge, if you do not do it. >> >> > >> >> > What I have done is this: >> >> > >> >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >> >> > # ifconfig wlan0 ssid ptamesh up >> >> > >> >> > Up to here works well. It will scan and if it finds another node with >> >> > the >> >> > same ssid, it will "lock" on that channel and use the correct bssid. >> >> > >> >> > If it does not find another node with the same ssid, it will start it >> >> > own thing on channel 10. But it looks like one cannot set the bssid. >> >> > >> >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >> >> > ifconfig: 02:07:ca:fe:ba:be: bad value >> >> >> >> I had similar experience with STA mode, instead I use ap (ap is alias >> >> for bssid, at least it works in STA mode) >> >> I never bothered is this bug in manual page, ifconfig or in something >> >> else >> >> ... >> > >> > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >> > Just do not try to unset it with "ifconfig wlan0 ap -". That is an >> > alias for "panic now" :-) >> Well, on my system it doesnt panic here. >> So more info to debug "your" panic is required ... > > I'll have to see if I can reproduce it. I managed to reproduce panic on recent CURRENT, with two cards in adhoc mode. rum0 (usb2) & ndis0 (personal hacked version without usb code) I typed "ifconfig wlan0 ap -" several times. bt: db:0:kdb.enter.unknown> run lockinfo db:1:lockinfo> show locks db:1:locks> show alllocks Process 1471 (ifconfig) thread 0xc4028690 (100048) Process 477 (syslogd) thread 0xc402b8c0 (100058) db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.unknown> show pcpu cpuid = 1 curthread = 0xc4028690: pid 1471 "ifconfig" curpcb = 0xe64e1d90 fpcurthread = none idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" APIC ID = 1 currentldt = 0x50 spin locks held: db:0:kdb.enter.unknown> bt Tracing pid 1471 tid 100048 td 0xc4028690 ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at ieee80211_ht_adjust_channel+0x30 adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at adhoc_pick_bss+0x100 ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at ieee80211_check_scan+0x20d ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at ieee80211_check_scan_current+0x45 adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at ieee80211_new_state_locked+0xc4 ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at ieee80211_init+0x45 ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) at ieee80211_ioctl_set80211+0xe5 in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at in_control+0xdc4 ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at soo_ioctl+0x397 kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 syscall(e64e1d38) at syscall+0x283 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = 0xbfbfe48c, ebp = 0xbfbfe4d8 --- here is panic message: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0a0c5b0 stack pointer = 0x28:0xe64e1980 frame pointer = 0x28:0xe64e1990 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1471 (ifconfig) exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 (0xc46a8014) locked @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 (0xc46a8014) locked @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ /usr/src/sys/kern/vfs_bio.c:2443 exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ /usr/src/sys/kern/vfs_vnops.c:593 0xc41a2000: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xc413aaa8 ref 0 pages 7 lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) ino 164881, on dev ad4s1d From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 17:51:11 2008 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 697CC1065699 for ; Fri, 26 Sep 2008 17:51:11 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 283F68FC08 for ; Fri, 26 Sep 2008 17:51:11 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8QHpAlB094287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Sep 2008 10:51:10 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DD210E.6050300@freebsd.org> Date: Fri, 26 Sep 2008 10:51:10 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: John Hay References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> In-Reply-To: <20080926055522.GA13842@zibbi.meraka.csir.co.za> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: "Paul B. Mahol" , freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Fri, 26 Sep 2008 17:51:11 -0000 John Hay wrote: > On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: > >> On 9/25/08, John Hay wrote: >> >>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>> >>>> On 9/22/08, John Hay wrote: >>>> >>>>> Hi >>>>> >>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>> an adhoc network because of problems that the network split and does >>>>> not merge, if you do not do it. >>>>> >>>>> What I have done is this: >>>>> >>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>> # ifconfig wlan0 ssid ptamesh up >>>>> >>>>> Up to here works well. It will scan and if it finds another node with >>>>> the >>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>> >>>>> If it does not find another node with the same ssid, it will start it >>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>> >>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>> >>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>> for bssid, at least it works in STA mode) >>>> I never bothered is this bug in manual page, ifconfig or in something else >>>> ... >>>> >>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>> alias for "panic now" :-) >>> >> Well, on my system it doesnt panic here. >> So more info to debug "your" panic is required ... >> > > I'll have to see if I can reproduce it. > > >>> So it looks like ifconfig is getting confused with the many different >>> uses of the keyword bssid. >>> >>> I must say I still do not understand what the other use for bssid is. >>> Close to the end of ifconfig/ifieee80211.c there are these: >>> >>> DEF_CMD_ARG("bssid", set80211bssid), >>> DEF_CMD_ARG("ap", set80211bssid), >>> ... >>> DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), >>> DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), >>> >>> So my guess is that I was hitting the clone version when in fact I >>> needed the other version. Luckily ap does not have a clone version. >>> So when should the clone version be used? And how does ifconfig >>> decide which one to use? >>> > > I looked into the ifconfig code a bit more. I think that with the > current code in the ifconfig() and cmd_lookup() functions, it is > imposssible to have two different keywords that share the same > keyword. cmd_lookup() will always search until it finds the first > instance in the list and return that. The first instance in this > case being the last one added. > Correct. > So either the code must change or one of the bssid keywords have > to change. My suggestion would be to keep the bssid for which ap > is an alias and change the other one. Anybody have a suggestion > of what to change it to? > > I prefer to change the code to handle this ambiguity within ifieee80211.c. You cannot use both together or at least they are redundant. I'll look at it when I've got time; but don't let me distract you. Sam From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 17:55:10 2008 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 2527E106568C for ; Fri, 26 Sep 2008 17:55:10 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id CC7198FC20 for ; Fri, 26 Sep 2008 17:55:09 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8QHt7xq094315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Sep 2008 10:55:09 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DD21FB.6060300@freebsd.org> Date: Fri, 26 Sep 2008 10:55:07 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: "Paul B. Mahol" References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> In-Reply-To: <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Fri, 26 Sep 2008 17:55:10 -0000 Paul B. Mahol wrote: > On 9/26/08, John Hay wrote: > >> On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >> >>> On 9/25/08, John Hay wrote: >>> >>>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>>> >>>>> On 9/22/08, John Hay wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>> an adhoc network because of problems that the network split and does >>>>>> not merge, if you do not do it. >>>>>> >>>>>> What I have done is this: >>>>>> >>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>> >>>>>> Up to here works well. It will scan and if it finds another node with >>>>>> the >>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>> >>>>>> If it does not find another node with the same ssid, it will start it >>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>> >>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>> >>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>> for bssid, at least it works in STA mode) >>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>> else >>>>> ... >>>>> >>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>> alias for "panic now" :-) >>>> >>> Well, on my system it doesnt panic here. >>> So more info to debug "your" panic is required ... >>> >> I'll have to see if I can reproduce it. >> > > I managed to reproduce panic on recent CURRENT, with two cards in adhoc mode. > rum0 (usb2) & ndis0 (personal hacked version without usb code) > > I typed "ifconfig wlan0 ap -" several times. > > > bt: > > db:0:kdb.enter.unknown> run lockinfo > db:1:lockinfo> show locks > db:1:locks> show alllocks > Process 1471 (ifconfig) thread 0xc4028690 (100048) > Process 477 (syslogd) thread 0xc402b8c0 (100058) > db:1:alllocks> show lockedvnods > Locked vnodes > db:0:kdb.enter.unknown> show pcpu > cpuid = 1 > curthread = 0xc4028690: pid 1471 "ifconfig" > curpcb = 0xe64e1d90 > fpcurthread = none > idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" > APIC ID = 1 > currentldt = 0x50 > spin locks held: > db:0:kdb.enter.unknown> bt > Tracing pid 1471 tid 100048 td 0xc4028690 > ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at > ieee80211_ht_adjust_channel+0x30 > adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at > adhoc_pick_bss+0x100 > ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at ieee80211_check_scan+0x20d > ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at > ieee80211_check_scan_current+0x45 > adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 > ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at > ieee80211_new_state_locked+0xc4 > ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at ieee80211_init+0x45 > ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) > at ieee80211_ioctl_set80211+0xe5 > in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at in_control+0xdc4 > ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a > soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at soo_ioctl+0x397 > kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd > ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 > syscall(e64e1d38) at syscall+0x283 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = > 0xbfbfe48c, ebp = 0xbfbfe4d8 --- > > here is panic message: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0a0c5b0 > stack pointer = 0x28:0xe64e1980 > frame pointer = 0x28:0xe64e1990 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1471 (ifconfig) > exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 > (0xc46a8014) locked @ > /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 > exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 > (0xc46a8014) locked @ > /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 > exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ > /usr/src/sys/kern/vfs_bio.c:2443 > exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ > /usr/src/sys/kern/vfs_vnops.c:593 > > 0xc41a2000: tag ufs, type VREG > usecount 1, writecount 1, refcount 4 mountedhere 0 > flags () > v_object 0xc413aaa8 ref 0 pages 7 > lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) > > ino 164881, on dev ad4s1d > Looks like adhoc_pick_channel returned NULL which was unexpected. Don't have a quick fix but it's possible no channel may be selected so the code is wrong. I rarely touch adhoc mode so this stuff is lightly tested. Sam From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 26 22:17:01 2008 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 6A61C106568B for ; Fri, 26 Sep 2008 22:17:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 382208FC14 for ; Fri, 26 Sep 2008 22:17:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1068861rvf.43 for ; Fri, 26 Sep 2008 15:17:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5HtGossa0PQ7nbSLu4xTlBmD7+v8Y/nWsu8TvycBQnI=; b=R3PB5KoLuqPiVVZTUvKvB/y8eBu+MQYKQrxq2KFKnItVW5R95m7Hx+EU4Z75dbZvMw yUrG0piV6avoiGev0P2Za8uhHPJFrAUB4ITuU9hkXnT4HYCEFdmAyoP7+rFayc7Kf+Y6 tavLWljyvFd9kiEue9n70XpFemcm0x9Bhy2Kc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fbVaO7fq1CT/IWwfiEsS6mDyIrMtGMBI+F77r2jmt9AjuD3v4NNDVp/ifGNvdbGVBB pmAJ6Y5ipZH9U23FKCWVc5dN7UoPTsbueCP/TiycWZjTYBQGvOhXLEa0YvIDtiXkZYBw axgLeLpIoURqs3RsXH3MTngwrTMclDHgTLsbI= Received: by 10.140.132.8 with SMTP id f8mr1021866rvd.198.1222467420561; Fri, 26 Sep 2008 15:17:00 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Fri, 26 Sep 2008 15:17:00 -0700 (PDT) Message-ID: <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> Date: Sat, 27 Sep 2008 00:17:00 +0200 From: "Paul B. Mahol" To: "Sam Leffler" In-Reply-To: <48DD21FB.6060300@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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: Fri, 26 Sep 2008 22:17:01 -0000 On 9/26/08, Sam Leffler wrote: > Paul B. Mahol wrote: >> On 9/26/08, John Hay wrote: >> >>> On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >>> >>>> On 9/25/08, John Hay wrote: >>>> >>>>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>>>> >>>>>> On 9/22/08, John Hay wrote: >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>>> an adhoc network because of problems that the network split and does >>>>>>> not merge, if you do not do it. >>>>>>> >>>>>>> What I have done is this: >>>>>>> >>>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>>> >>>>>>> Up to here works well. It will scan and if it finds another node with >>>>>>> the >>>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>>> >>>>>>> If it does not find another node with the same ssid, it will start it >>>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>>> >>>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>>> >>>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>>> for bssid, at least it works in STA mode) >>>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>>> else >>>>>> ... >>>>>> >>>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>>> alias for "panic now" :-) >>>>> >>>> Well, on my system it doesnt panic here. >>>> So more info to debug "your" panic is required ... >>>> >>> I'll have to see if I can reproduce it. >>> >> >> I managed to reproduce panic on recent CURRENT, with two cards in adhoc >> mode. >> rum0 (usb2) & ndis0 (personal hacked version without usb code) >> >> I typed "ifconfig wlan0 ap -" several times. >> >> >> bt: >> >> db:0:kdb.enter.unknown> run lockinfo >> db:1:lockinfo> show locks >> db:1:locks> show alllocks >> Process 1471 (ifconfig) thread 0xc4028690 (100048) >> Process 477 (syslogd) thread 0xc402b8c0 (100058) >> db:1:alllocks> show lockedvnods >> Locked vnodes >> db:0:kdb.enter.unknown> show pcpu >> cpuid = 1 >> curthread = 0xc4028690: pid 1471 "ifconfig" >> curpcb = 0xe64e1d90 >> fpcurthread = none >> idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" >> APIC ID = 1 >> currentldt = 0x50 >> spin locks held: >> db:0:kdb.enter.unknown> bt >> Tracing pid 1471 tid 100048 td 0xc4028690 >> ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at >> ieee80211_ht_adjust_channel+0x30 >> adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at >> adhoc_pick_bss+0x100 >> ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at >> ieee80211_check_scan+0x20d >> ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at >> ieee80211_check_scan_current+0x45 >> adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 >> ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at >> ieee80211_new_state_locked+0xc4 >> ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at >> ieee80211_init+0x45 >> ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) >> at ieee80211_ioctl_set80211+0xe5 >> in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at >> in_control+0xdc4 >> ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a >> soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at >> soo_ioctl+0x397 >> kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd >> ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 >> syscall(e64e1d38) at syscall+0x283 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = >> 0xbfbfe48c, ebp = 0xbfbfe4d8 --- >> >> here is panic message: >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x0 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc0a0c5b0 >> stack pointer = 0x28:0xe64e1980 >> frame pointer = 0x28:0xe64e1990 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 1471 (ifconfig) >> exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 >> (0xc46a8014) locked @ >> /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 >> exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 >> (0xc46a8014) locked @ >> /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 >> exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ >> /usr/src/sys/kern/vfs_bio.c:2443 >> exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ >> /usr/src/sys/kern/vfs_vnops.c:593 >> >> 0xc41a2000: tag ufs, type VREG >> usecount 1, writecount 1, refcount 4 mountedhere 0 >> flags () >> v_object 0xc413aaa8 ref 0 pages 7 >> lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) >> >> ino 164881, on dev ad4s1d >> > Looks like adhoc_pick_channel returned NULL which was unexpected. Don't > have a quick fix but it's possible no channel may be selected so the > code is wrong. I rarely touch adhoc mode so this stuff is lightly tested. On further investigation it appears to be locking problem - I was not able to reproduce panic with kern.smp.disabled=1 From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 07:10:49 2008 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 10AF21065688; Sat, 27 Sep 2008 07:10:49 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD778FC08; Sat, 27 Sep 2008 07:10:48 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 3F21E33CD6; Sat, 27 Sep 2008 09:10:46 +0200 (SAST) Date: Sat, 27 Sep 2008 09:10:46 +0200 From: John Hay To: Sam Leffler Message-ID: <20080927071046.GA94774@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <48DD210E.6050300@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48DD210E.6050300@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 27 Sep 2008 07:10:49 -0000 > >>>>> > >>>>>I'm trying out the new ath/wlan stuff in current. Should one still be > >>>>>able to set the bssid in adhoc mode? We normally lock the bssid in > >>>>>an adhoc network because of problems that the network split and does > >>>>>not merge, if you do not do it. > >>>>> > >>>>>What I have done is this: > >>>>> > >>>>># ifconfig wlan0 create wlandev ath0 wlanmode adhoc > >>>>># ifconfig wlan0 ssid ptamesh up > >>>>> > >>>>>Up to here works well. It will scan and if it finds another node with > >>>>>the > >>>>>same ssid, it will "lock" on that channel and use the correct bssid. > >>>>> > >>>>>If it does not find another node with the same ssid, it will start it > >>>>>own thing on channel 10. But it looks like one cannot set the bssid. > >>>>> > >>>>># ifconfig wlan0 bssid 02:07:ca:fe:ba:be > >>>>>ifconfig: 02:07:ca:fe:ba:be: bad value > >>>>> > >>>>I had similar experience with STA mode, instead I use ap (ap is alias > >>>>for bssid, at least it works in STA mode) > >>>>I never bothered is this bug in manual page, ifconfig or in something > >>>>else > >>>>... > >>>> > >>>Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > >>>Just do not try to unset it with "ifconfig wlan0 ap -". That is an > >>>alias for "panic now" :-) > >>> > >>Well, on my system it doesnt panic here. > >>So more info to debug "your" panic is required ... > >> > > > >I'll have to see if I can reproduce it. > > > > > >>>So it looks like ifconfig is getting confused with the many different > >>>uses of the keyword bssid. > >>> > >>>I must say I still do not understand what the other use for bssid is. > >>>Close to the end of ifconfig/ifieee80211.c there are these: > >>> > >>>DEF_CMD_ARG("bssid", set80211bssid), > >>>DEF_CMD_ARG("ap", set80211bssid), > >>>... > >>>DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > >>>DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > >>> > >>>So my guess is that I was hitting the clone version when in fact I > >>>needed the other version. Luckily ap does not have a clone version. > >>>So when should the clone version be used? And how does ifconfig > >>>decide which one to use? > >>> > > > >I looked into the ifconfig code a bit more. I think that with the > >current code in the ifconfig() and cmd_lookup() functions, it is > >imposssible to have two different keywords that share the same > >keyword. cmd_lookup() will always search until it finds the first > >instance in the list and return that. The first instance in this > >case being the last one added. > > > > Correct. > > >So either the code must change or one of the bssid keywords have > >to change. My suggestion would be to keep the bssid for which ap > >is an alias and change the other one. Anybody have a suggestion > >of what to change it to? > > > > > I prefer to change the code to handle this ambiguity within > ifieee80211.c. You cannot use both together or at least they are > redundant. I'll look at it when I've got time; but don't let me > distract you. So what should the behaviour be? How should ifconfig know which bssid function to use? Should the clone variant be used when it is used on the same line as create? And the other if there is not a create on the line? Or some other way? And should the other DEF_CLONE... keywords also be handled the same way? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 13:02:07 2008 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 C4D101065699 for ; Sat, 27 Sep 2008 13:02:07 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 933FF8FC12 for ; Sat, 27 Sep 2008 13:02:07 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1254567rvf.43 for ; Sat, 27 Sep 2008 06:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=FwWciaj9TlHdrpWYoGFld1Nk/fIqJlCTLnZz7OV1UPI=; b=By+XdCltQTXrCQGt9HXmuB1Z/1iFDh+PcBbdZZ/xkYH9fMMjEdktVuNqIeAdAwiIir YNulwsZ5qxjJiUWox74wEikntAVvNd4iwJwCKVktvnG5oBB/BTGK04ZKxNgOFBZenKkt odY+g4tBBo9HPWb2+LJUsjkXHX2p8nrpr7vds= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=efE92U51X82G4D/4lzNMv1QndislHFw4vuflyrkMdp3zCbXd7A8RvolLsEndquz06a gB7oMoXenP3Hu7SrSb7BVIGXe09EDcaRT6PgC71AyouTQXIPmdxLfxEl3f/JlUrGHIZD OBmwcbASvThClrr2FjfdLTx8drdlT0yzKoa4c= Received: by 10.141.132.8 with SMTP id j8mr1339866rvn.90.1222520527183; Sat, 27 Sep 2008 06:02:07 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Sat, 27 Sep 2008 06:02:07 -0700 (PDT) Message-ID: <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> Date: Sat, 27 Sep 2008 15:02:07 +0200 From: "Paul B. Mahol" To: "Sam Leffler" In-Reply-To: <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 27 Sep 2008 13:02:07 -0000 On 9/27/08, Paul B. Mahol wrote: > On further investigation it appears to be locking problem - I was not > able to reproduce panic with kern.smp.disabled=1 Wrong, kernel still panic in same place when putting wlan0 several time up and down. (without adding "ap -" at all) So adhoc is broken in CURRENT. From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 19:16:04 2008 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 8A9491065687 for ; Sat, 27 Sep 2008 19:16:04 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 48C668FC19 for ; Sat, 27 Sep 2008 19:16:04 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8RJG0qv001780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Sep 2008 12:16:03 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DE8670.60606@freebsd.org> Date: Sat, 27 Sep 2008 12:16:00 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: John Hay References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <48DD210E.6050300@freebsd.org> <20080927071046.GA94774@zibbi.meraka.csir.co.za> In-Reply-To: <20080927071046.GA94774@zibbi.meraka.csir.co.za> Content-Type: multipart/mixed; boundary="------------020202030001020600070906" X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 27 Sep 2008 19:16:04 -0000 This is a multi-part message in MIME format. --------------020202030001020600070906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit John Hay wrote: >>>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>>> an adhoc network because of problems that the network split and does >>>>>>> not merge, if you do not do it. >>>>>>> >>>>>>> What I have done is this: >>>>>>> >>>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>>> >>>>>>> Up to here works well. It will scan and if it finds another node with >>>>>>> the >>>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>>> >>>>>>> If it does not find another node with the same ssid, it will start it >>>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>>> >>>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>>> >>>>>>> >>>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>>> for bssid, at least it works in STA mode) >>>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>>> else >>>>>> ... >>>>>> >>>>>> >>>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>>> alias for "panic now" :-) >>>>> >>>>> >>>> Well, on my system it doesnt panic here. >>>> So more info to debug "your" panic is required ... >>>> >>>> >>> I'll have to see if I can reproduce it. >>> >>> >>> >>>>> So it looks like ifconfig is getting confused with the many different >>>>> uses of the keyword bssid. >>>>> >>>>> I must say I still do not understand what the other use for bssid is. >>>>> Close to the end of ifconfig/ifieee80211.c there are these: >>>>> >>>>> DEF_CMD_ARG("bssid", set80211bssid), >>>>> DEF_CMD_ARG("ap", set80211bssid), >>>>> ... >>>>> DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), >>>>> DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), >>>>> >>>>> So my guess is that I was hitting the clone version when in fact I >>>>> needed the other version. Luckily ap does not have a clone version. >>>>> So when should the clone version be used? And how does ifconfig >>>>> decide which one to use? >>>>> >>>>> >>> I looked into the ifconfig code a bit more. I think that with the >>> current code in the ifconfig() and cmd_lookup() functions, it is >>> imposssible to have two different keywords that share the same >>> keyword. cmd_lookup() will always search until it finds the first >>> instance in the list and return that. The first instance in this >>> case being the last one added. >>> >>> >> Correct. >> >> >>> So either the code must change or one of the bssid keywords have >>> to change. My suggestion would be to keep the bssid for which ap >>> is an alias and change the other one. Anybody have a suggestion >>> of what to change it to? >>> >>> >>> >> I prefer to change the code to handle this ambiguity within >> ifieee80211.c. You cannot use both together or at least they are >> redundant. I'll look at it when I've got time; but don't let me >> distract you. >> > > So what should the behaviour be? How should ifconfig know which bssid > function to use? Should the clone variant be used when it is used on > the same line as create? And the other if there is not a create on the > line? Or some other way? And should the other DEF_CLONE... keywords > also be handled the same way? > > John > Try the attached change. It looked easier to fix this for all possible usage instead of complicating the 802.11 stuff. The change forces all keywords marked "DEF_CLONE" to come first on the command line followed by keywords that are marked !DEF_CLONE. At some point it's likely we'll need to stick a real parser in ifconfig but I think this change is small enough to just do it this way (it also slightly cleans up the hack for pushing the clone operation out before parsing/handling subsequent cmd line args). Sam --------------020202030001020600070906 Content-Type: text/plain; name="ifconfig.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ifconfig.patch" Index: ifconfig.c =================================================================== --- ifconfig.c (revision 183416) +++ ifconfig.c (working copy) @@ -392,14 +392,21 @@ } static const struct cmd * -cmd_lookup(const char *name) +cmd_lookup(const char *name, int iscreate) { #define N(a) (sizeof(a)/sizeof(a[0])) const struct cmd *p; for (p = cmds; p != NULL; p = p->c_next) - if (strcmp(name, p->c_name) == 0) - return p; + if (strcmp(name, p->c_name) == 0) { + if (iscreate) { + if (p->c_iscloneop) + return p; + } else { + if (!p->c_iscloneop) + return p; + } + } return NULL; #undef N } @@ -437,6 +444,7 @@ ifconfig(int argc, char *const *argv, int iscreate, const struct afswtch *afp) { const struct afswtch *nafp; + const struct cmd *p; struct callback *cb; int s; @@ -452,9 +460,38 @@ err(1, "socket(family %u,SOCK_DGRAM", ifr.ifr_addr.sa_family); while (argc > 0) { - const struct cmd *p; - - p = cmd_lookup(*argv); + p = cmd_lookup(*argv, iscreate); + if (iscreate && p == NULL) { + /* + * Push the clone create callback so the new + * device is created and can be used for any + * remaining arguments. + */ + cb = callbacks; + if (cb == NULL) + errx(1, "internal error, no callback"); + callbacks = cb->cb_next; + cb->cb_func(s, cb->cb_arg); + iscreate = 0; + /* + * Handle any address family spec that + * immediately follows and potentially + * recreate the socket. + */ + nafp = af_getbyname(*argv); + if (nafp != NULL) { + argc--, argv++; + if (nafp != afp) { + close(s); + afp = nafp; + goto top; + } + } + /* + * Look for a normal parameter. + */ + continue; + } if (p == NULL) { /* * Not a recognized command, choose between setting @@ -463,33 +500,6 @@ p = (setaddr ? &setifdstaddr_cmd : &setifaddr_cmd); } if (p->c_u.c_func || p->c_u.c_func2) { - if (iscreate && !p->c_iscloneop) { - /* - * Push the clone create callback so the new - * device is created and can be used for any - * remaining arguments. - */ - cb = callbacks; - if (cb == NULL) - errx(1, "internal error, no callback"); - callbacks = cb->cb_next; - cb->cb_func(s, cb->cb_arg); - iscreate = 0; - /* - * Handle any address family spec that - * immediately follows and potentially - * recreate the socket. - */ - nafp = af_getbyname(*argv); - if (nafp != NULL) { - argc--, argv++; - if (nafp != afp) { - close(s); - afp = nafp; - goto top; - } - } - } if (p->c_parameter == NEXTARG) { if (argv[1] == NULL) errx(1, "'%s' requires argument", --------------020202030001020600070906-- From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 19:16:37 2008 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 10D6310656A6 for ; Sat, 27 Sep 2008 19:16:37 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id D7AE68FC2B for ; Sat, 27 Sep 2008 19:16:36 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8RJGZIs001791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Sep 2008 12:16:36 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DE8693.3000107@freebsd.org> Date: Sat, 27 Sep 2008 12:16:35 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: "Paul B. Mahol" References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> In-Reply-To: <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 27 Sep 2008 19:16:37 -0000 Paul B. Mahol wrote: > On 9/27/08, Paul B. Mahol wrote: > >> On further investigation it appears to be locking problem - I was not >> able to reproduce panic with kern.smp.disabled=1 >> > > Wrong, kernel still panic in same place when putting wlan0 several > time up and down. > (without adding "ap -" at all) > > So adhoc is broken in CURRENT. > _______________________________________________ > Well if you're telling me I'm wrong then I'll happily leave the issue to you. Sam From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 20:14:15 2008 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 AADDF106568C for ; Sat, 27 Sep 2008 20:14:15 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 773CF8FC1F for ; Sat, 27 Sep 2008 20:14:15 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1353252rvf.43 for ; Sat, 27 Sep 2008 13:14:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=domTjEVoan3IJ1HcqssSv1+P+lOmBGyRNHlrbB7fI+o=; b=Zkf96w4BHPu8wkyVvVsK3JKVrVB9RrK0xMQ5pibUSHWJ+VhRXXwZVmIuWnAiNd6WKF B9pza0wmQYiQpPdrpQ56jHIg55ZgFRAQn3JQFO6cCvM0LOdAeaWctpQW02XJwW8ZLHS/ xW9MpgiZuoD+r+bQGObSP3smCEuB1ZQ2i2BcQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JIiBGot23UDDsdS9u1WnnjfCE2WRw8JKaL/FNa8CjX/UGH5B7vGTNw4t2JirnlTJDm 7+8tsPvGr45jxo3xgu0EEET/Ezf+Gznj2qLsQcMVm1huTwBa0K6+30Kowj2j3Lu/PYGe xSM+g7/0Sz/lMXS2oYWRYb2aOlsfCZzRcJEqs= Received: by 10.141.107.13 with SMTP id j13mr1486426rvm.276.1222546455179; Sat, 27 Sep 2008 13:14:15 -0700 (PDT) Received: by 10.141.189.15 with HTTP; Sat, 27 Sep 2008 13:14:15 -0700 (PDT) Message-ID: <3a142e750809271314k6e9a75euc8952bda6fc5e61d@mail.gmail.com> Date: Sat, 27 Sep 2008 22:14:15 +0200 From: "Paul B. Mahol" To: "Sam Leffler" In-Reply-To: <48DE8693.3000107@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> <48DE8693.3000107@freebsd.org> Cc: freebsd-mobile@freebsd.org Subject: Re: setting bssid in adhoc mode 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, 27 Sep 2008 20:14:15 -0000 On 9/27/08, Sam Leffler wrote: > Paul B. Mahol wrote: >> On 9/27/08, Paul B. Mahol wrote: >> >>> On further investigation it appears to be locking problem - I was not >>> able to reproduce panic with kern.smp.disabled=1 >>> >> >> Wrong, kernel still panic in same place when putting wlan0 several >> time up and down. >> (without adding "ap -" at all) >> >> So adhoc is broken in CURRENT. >> _______________________________________________ >> > Well if you're telling me I'm wrong then I'll happily leave the issue to > you. No, you are correct. channel list seems to be populated with nulls, because there are free channels but null is still picked. From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 21:43:08 2008 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 E57261065688; Sat, 27 Sep 2008 21:43:08 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id E48138FC08; Sat, 27 Sep 2008 21:43:07 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.1.14) with ESMTPSA id 222571166; Sat, 27 Sep 2008 23:43:05 +0300 Message-ID: <48DEA8E7.2080503@FreeBSD.org> Date: Sun, 28 Sep 2008 00:43:03 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.16 (X11/20080726) MIME-Version: 1.0 To: freebsd-arm@FreeBSD.org, freebsd-mobile@FreeBSD.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: imp@FreeBSD.org Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements 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, 27 Sep 2008 21:43:09 -0000 Hi. I would like to present initial revision of my generic PCI SD Host Controller driver (sdhci). It support PCI devices with class 8 and subclass 5 according to SD Host Controller Specification. With some limitations it successfully works on my Acer TM6292 notebook with ENE CB714 card reader. Things that are working now: - PIO mode single and multiple block read and write, - 1 and 4 bits bus width support. In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) linear write. Small blocks read/write performance limited by card. Things that are not working yet: - DMA modes (code is written, but as my controller looks like has broken DMA I have no ability to debug it), - card insert/remove detection (need more thinking), you should reload mmc module to rescan cards, - SDHC and MMC cards (have no such cards now to debug that code), only standard capacity SD Memory cards up to 4GB size are supported now, - high speed (double rate) bus mode (need more thinking and DMA support). Also to get such results I have improved existing mmc and mmcsd drivers a bit. mmc driver got: - 4 bit bus width support, - write protection switch support, - cards with more then 2GB capacity support. mmcsd driver got: - multiple block read and write support, - cards with more then 2GB capacity support, - I/O error reporting, - write protection switch support. Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found at: http://people.freebsd.org/~mav/sdhci/ I will be grateful for any feedbacks, comments and support. -- Alexander Motin From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 21:52:34 2008 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 5816C10656C0; Sat, 27 Sep 2008 21:52:34 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from core.tav.kiev.ua (tavex.colocall.com [62.149.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id E61028FC1B; Sat, 27 Sep 2008 21:52:33 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from s01060021299bf294.vc.shawcable.net ([24.87.45.120] helo=jeeves.bluezbox.com) by core.tav.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1KjhJ0-000Osq-G8; Sun, 28 Sep 2008 00:26:23 +0300 Message-ID: <48DEA4EC.3030300@bluezbox.com> Date: Sat, 27 Sep 2008 14:26:04 -0700 From: Oleksandr Tymoshenko User-Agent: Thunderbird 2.0.0.16 (X11/20080831) MIME-Version: 1.0 To: Alexander Motin References: <48DEA8E7.2080503@FreeBSD.org> In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Core-Spam-Level: ---- X-Core-Spam-Report: Spam detection software, running on the system "core.tav.kiev.ua", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Alexander Motin wrote: > Hi. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found > at: > http://people.freebsd.org/~mav/sdhci/ Thanks! That's just what I was looking for about three weeks ago :) > > I will be grateful for any feedbacks, comments and support. 7.1 requires s/kproc/kthread/ but otherwise works fine: [...] Content analysis details: (-4.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.4 AWL AWL: From: address is in the auto white-list Cc: freebsd-arm@FreeBSD.org, freebsd-current@freebsd.org, imp@FreeBSD.org, freebsd-mobile@FreeBSD.org Subject: Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements 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, 27 Sep 2008 21:52:34 -0000 Alexander Motin wrote: > Hi. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found > at: > http://people.freebsd.org/~mav/sdhci/ Thanks! That's just what I was looking for about three weeks ago :) > > I will be grateful for any feedbacks, comments and support. 7.1 requires s/kproc/kthread/ but otherwise works fine: sdhci0: mem 0xff9fb800-0xff9fb8ff irq 9 at device 1.2 on pci2 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] mmc0: on sdhci0 mmc0: SD card: 507379712 bytes mmcsd0: 483MB (read-only) at mmc0 mmc0: setting transfer rate to 30.000MHz mmc0: setting bus width to 4 bits GEOM_LABEL: Label for provider mmcsd0s1 is msdosfs/SD. From owner-freebsd-mobile@FreeBSD.ORG Sat Sep 27 22:59:13 2008 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 80DFD106569C for ; Sat, 27 Sep 2008 22:59:13 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB7C8FC13 for ; Sat, 27 Sep 2008 22:59:12 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so539673nfh.33 for ; Sat, 27 Sep 2008 15:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc:from:sender; bh=MisK+0IjqFwDBUzwm3/2/8jAhy0EWNoVIdUqw3fV/wg=; b=bZ9Cg7zccNqijrJhUk94ATotUp9J2+WVgsZn1FiyJG00kZkWrXfyFtHRjP5JPkSEbu A0jdW8nVX3Mxu/af3gm/mzMKbI/G5QPPVls1Zekdz0Ost7XnJ88lUMa+cV+TLOoe+qvU w738hqbYqKNnEXGZ300spp1s3oTRFjrv7URJM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc :from:sender; b=d16NKjvgInxtbXIeXrZvadDjYjFnbu9d8+Z2Mnp+HhmlRfPTRZEtf/z4JjKpLKb2qT l3mVVASC0VaH+oH6OJvyPwZO1bTe38VBux51Sd74TGNbkNtiSqlPRRPBJAw3TdWiCPwa WQ271kqAeBSLvSryPEzbkYfn430QI/w6GFZjA= Received: by 10.210.87.14 with SMTP id k14mr3806217ebb.7.1222556351614; Sat, 27 Sep 2008 15:59:11 -0700 (PDT) Received: from ?10.0.1.4? ([89.214.188.107]) by mx.google.com with ESMTPS id q9sm867075gve.5.2008.09.27.15.59.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 27 Sep 2008 15:59:10 -0700 (PDT) References: <48DEA8E7.2080503@FreeBSD.org> Message-Id: <9D33158B-B28D-4D22-B3BF-A7CE376FCAD1@freebd.org> To: Alexander Motin In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPod Mail (5F137) Mime-Version: 1.0 (iPod Mail 5F137) Date: Sat, 27 Sep 2008 23:58:56 +0100 From: Rui Paulo Sender: Rui Paulo Cc: "freebsd-arm@FreeBSD.org" , "freebsd-current@freebsd.org" , "imp@FreeBSD.org" , "freebsd-mobile@FreeBSD.org" Subject: Re: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements 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, 27 Sep 2008 22:59:13 -0000 On 27 Sep 2008, at 22:43, Alexander Motin wrote: > Hi. > > I would like to present initial revision of my generic PCI SD Host > Controller driver (sdhci). It support PCI devices with class 8 and > subclass 5 according to SD Host Controller Specification. With some > limitations it successfully works on my Acer TM6292 notebook with > ENE CB714 card reader. > > Things that are working now: > - PIO mode single and multiple block read and write, > - 1 and 4 bits bus width support. > > In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about > 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) > linear write. Small blocks read/write performance limited by card. > > Things that are not working yet: > - DMA modes (code is written, but as my controller looks like has > broken DMA I have no ability to debug it), > - card insert/remove detection (need more thinking), you should > reload mmc module to rescan cards, > - SDHC and MMC cards (have no such cards now to debug that code), > only standard capacity SD Memory cards up to 4GB size are supported > now, > - high speed (double rate) bus mode (need more thinking and DMA > support). > > Also to get such results I have improved existing mmc and mmcsd > drivers a bit. mmc driver got: > - 4 bit bus width support, > - write protection switch support, > - cards with more then 2GB capacity support. > mmcsd driver got: > - multiple block read and write support, > - cards with more then 2GB capacity support, > - I/O error reporting, > - write protection switch support. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be > found at: > http://people.freebsd.org/~mav/sdhci/ > > I will be grateful for any feedbacks, comments and support. Well, here's my support: Great work! :-) -- Rui Paulo