From nobody@FreeBSD.org  Thu Nov 20 19:13:23 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AC5481065670
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 20 Nov 2008 19:13:23 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 97EAD8FC1C
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 20 Nov 2008 19:13:23 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mAKJDNDg076951
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 20 Nov 2008 19:13:23 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id mAKJDNV6076950;
	Thu, 20 Nov 2008 19:13:23 GMT
	(envelope-from nobody)
Message-Id: <200811201913.mAKJDNV6076950@www.freebsd.org>
Date: Thu, 20 Nov 2008 19:13:23 GMT
From: Alex <freebsd.alex@spamfoodie.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: ath cannot connect using WEP
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         129022
>Category:       kern
>Synopsis:       [ath] ath cannot connect using WEP
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    sam
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 20 19:20:03 UTC 2008
>Closed-Date:    Sun Dec 14 02:44:46 UTC 2008
>Last-Modified:  Sun Dec 14 02:44:46 UTC 2008
>Originator:     Alex
>Release:        8-CURRENT
>Organization:
>Environment:
FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Thu Nov 20 16:58:53 CET 2008     root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL  i386
>Description:
i'm not able to connect to my router using WEP encryption. if i disable
encryption in my router i'm able to connect without any problems.

i'm using the following wifi-card:

ath0@pci0:5:1:0:        class=0x020000 card=0x5a001385 chip=0x0013168c rev=0x01 hdr=0x00
    vendor     = 'Atheros Communications Inc.'
    device     = 'AR5212, AR5213 802.11a/b/g Wireless Adapter'
    class      = network
    subclass   = ethernet



my rc.conf contains the following wlan related entries:

wlans_ath0=wlan0
ifconfig_wlan0="inet 192.168.1.10 ssid XXXXXX wepmode on authmode shared wepkey 1:0xXXXXXXXXXXXXXXXXXXXXXXXXXX wepkey 2:- wepkey 3:- wepkey 4:- deftxkey 1 channel 11"



this is the output from ifconfig:

ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether XX:XX:XX:XX:XX:XX
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
        status: associated
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
wlan0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether XX:XX:XX:XX:XX:XX
        inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
        ssid XXXXXX channel 11 (2462 Mhz 11g)
        country US ecm authmode SHARED privacy ON deftxkey 1 wepkey 1:104-bit
        txpower 18.5 bmiss 7 scanvalid 60 bgscan bgscanintvl 300
        bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst ff
        dturbo



enabling wlan debugging using wlandebug scan+auth+assoc revealed the following errors:

Nov 20 19:24:58 moshnroll kernel: wlan0: notify scan done
Nov 20 19:24:58 moshnroll kernel: wlan0: [XX:XX:XX:XX:XX:XX] recv auth frame with algorithm 1 seq 2
Nov 20 19:24:58 moshnroll kernel: wlan0: [XX:XX:XX:XX:XX:XX] request encrypt frame (ieee80211_send_mgmt)
Nov 20 19:24:58 moshnroll kernel: wlan0: [XX:XX:XX:XX:XX:XX] encrypting frame (ieee80211_mgmt_output)
Nov 20 19:25:00 moshnroll kernel: wlan0: [XX:XX:XX:XX:XX:XX] ieee80211_scan_assoc_fail: reason 1
Nov 20 19:25:00 moshnroll kernel: wlan0: [XX:XX:XX:XX:XX:XX] sta_assoc_fail: reason 1 fails 2

please tell me if you need more info from the debug output.

here're the outputs of

athstats:

athstats: ath0: Invalid argument
athstats: ath0: Invalid argument
25206    data frames received
5286     data frames transmit
7        tx frames with an alternate rate
53       long on-chip tx retries
4        tx failed 'cuz too many retries
8554     mib overflow interrupts
1M       current transmit rate
108      tx frames with short preamble
663      rx failed 'cuz of bad CRC
36       rx failed 'cuz of PHY err
    36       CCK restart
15       periodic calibrations
30       rssi of last ack
20       avg recv rssi
-96      rx noise floor
4        fast frames flushed from staging q
Antenna profile:
[1] tx     3775 rx    25206
[2] tx     1509 rx        0



and wlanstats:

wlanstats: wlan0 (IEEE80211_IOC_STA_INFO): No such file or directory
wlanstats: wlan0 (IEEE80211_IOC_STA_STATS): No such file or directory
2002     rx from wrong bssid
3        rx discard 'cuz dup
2135     rx discard mgt frames
161      rx beacon frames
186      rx element unknown
1        rx discard 'cuz port unauthorized
107      active scans started
2618     rx management frames
1        tx failed 'cuz vap not in RUN state
0M       current transmit rate

cheers.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Nov 20 22:41:44 UTC 2008 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=129022 

From: Alex <freebsd.alex@spamfoodie.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/129022: [ath] ath cannot connect using WEP
Date: Fri, 28 Nov 2008 12:26:59 GMT

 >Submitter-Id:	current-users
 >Originator:	Alex
 >Organization:	
 >Confidential:	no
 >Synopsis:	Re: kern/129022: [ath] ath cannot connect using WEP
 >Severity:	serious
 >Priority:	high
 >Category:	kern
 >Class:		sw-bug
 >Release:	8-CURRENT
 >Environment:	FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #8 r185353M: Thu Nov 27 01:48:42 CET 2008     root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL  i386
 >Description:
 could somebody please have a look at this? just tell me if you need more debug output and i'll provide it. right now i have to connect to my router using no encryption at all which obviously is far from save.
 
 thanks in advance.
 >How-To-Repeat:
 
 >Fix:
 
 
Responsible-Changed-From-To: freebsd-net->sam 
Responsible-Changed-By: sam 
Responsible-Changed-When: Fri Nov 28 18:13:53 UTC 2008 
Responsible-Changed-Why:  
didn't know this existed; will check 

http://www.freebsd.org/cgi/query-pr.cgi?pr=129022 

From: Alex <freebsd.alex@spamfoodie.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/129022: [ath] ath cannot connect using WEP
Date: Tue, 2 Dec 2008 14:49:57 GMT

 >Submitter-Id:	current-users
 >Originator:	Alex
 >Organization:	
 >Confidential:	no
 >Synopsis:	Re: kern/129022: [ath] ath cannot connect using WEP
 >Severity:	serious
 >Priority:	high
 >Category:	misc
 >Class:		sw-bug
 >Release:	8-CURRENT
 >Environment:	FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #11 r185532M: Mon Dec  1 23:16:26 CET 2008     root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL  i386
 >Description:
 i rebuild the kernel yesterday with fresh sources. i'm still unable to connect to my router using wep. so the recent changes in ath (new open source ath_hal e.g.) didn't fix this issue.
 
 cheers.
 >How-To-Repeat:
 
 >Fix:
 
 

From: Alex <freebsd.alex@spamfoodie.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/129022: [ath] ath cannot connect using WEP
Date: Wed, 3 Dec 2008 00:38:41 GMT

 >Submitter-Id:	current-users
 >Originator:	Alex
 >Organization:	
 >Confidential:	no
 >Synopsis:	Re: kern/129022: [ath] ath cannot connect using WEP
 >Severity:	serious
 >Priority:	high
 >Category:	kern
 >Class:		sw-bug
 >Release:	8-CURRENT
 >Environment:	FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #12 r185549M: Wed Dec  3 01:01:34 CET 2008     root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL  i386
 >Description:
 here's a discussion in @current which seems to be dealing with the very same problem i am having. i tried to see if connecting with wpa_supplicant works and i get the same error message described in this thread:
 
 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=83807+0+/usr/local/www/db/text/2008/freebsd-current/20080525.freebsd-current
 
 when i run wpa_supplicant i get the following output:
 
 ioctl[SIOCS80211, op 103, len 128]: Device not configured
 Failed to initiate AP scan.
 
 if i apply the patch from this post: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=146030+0+/usr/local/www/db/text/2008/freebsd-current/20080525.freebsd-current the error messages dissapears, but wpa_supplicant tells me that it's unable do disable WPA.
 
 cheers.
 >How-To-Repeat:
 
 >Fix:
 
 

From: Alex <freebsd.alex@spamfoodie.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/129022: [ath] ath cannot connect using WEP
Date: Tue, 9 Dec 2008 00:09:49 GMT

 >Submitter-Id:	current-users
 >Originator:	Alex
 >Organization:	
 >Confidential:	no
 >Synopsis:	Re: kern/129022: [ath] ath cannot connect using WEP
 >Severity:	non-critical
 >Priority:	low
 >Category:	misc
 >Class:		sw-bug
 >Release:	
 >Environment:	
 >Description:
 this PR can be closed.
 >How-To-Repeat:
 
 >Fix:
 
 

From: Alexander Best <alexbestms@math.uni-muenster.de>
To: <bug-followup@FreeBSD.org>,
 <freebsd.alex@spamfoodie.com>
Cc:  
Subject: Re: kern/129022: [ath] ath cannot connect using WEP
Date: Tue, 09 Dec 2008 01:11:51 +0100 (CET)

 this PR can be closed.
State-Changed-From-To: open->closed 
State-Changed-By: sam 
State-Changed-When: Sun Dec 14 02:44:28 UTC 2008 
State-Changed-Why:  
fix committed to HEAD 

http://www.freebsd.org/cgi/query-pr.cgi?pr=129022 
>Unformatted:
