From nobody@FreeBSD.org  Thu Feb 14 08:24:02 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 7C84816A41B
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Feb 2008 08:24:02 +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 459E013C43E
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Feb 2008 08:24:02 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m1E8LhVf079195
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 14 Feb 2008 08:21:43 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m1E8LhU2079194;
	Thu, 14 Feb 2008 08:21:43 GMT
	(envelope-from nobody)
Message-Id: <200802140821.m1E8LhU2079194@www.freebsd.org>
Date: Thu, 14 Feb 2008 08:21:43 GMT
From: Yuri <yuri@tsoft.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         120636
>Category:       kern
>Synopsis:       Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    vwe
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 14 08:30:01 UTC 2008
>Closed-Date:    Wed May 14 21:05:39 UTC 2008
>Last-Modified:  Wed May 14 21:05:39 UTC 2008
>Originator:     Yuri
>Release:        7.0-PERLEASE
>Organization:
n/a
>Environment:
>Description:
It was able to connect to both unencrypted and encrypted networks few times.
Then while attempting to bring it up with incorrect wepkey all system hanged.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: "Remko Lodder" <remko@elvandar.org>
To: "Yuri" <yuri@tsoft.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/120636: Ndis driver causes system to hang while bringing 
     AirLink101-AWLC3026 card up
Date: Thu, 14 Feb 2008 09:44:40 +0100 (CET)

 > It was able to connect to both unencrypted and encrypted networks few
 > times.
 > Then while attempting to bring it up with incorrect wepkey all system
 > hanged.
 >
 
 Nice, even less info and we can start working on this. Ow no my mistake,
 the other way around ofcourse.
 
 Can you provide a boot-verbose, dmesg kernel messages when the attach
 works etc etc so that we can see how the system looks like. Does the
 wepkey at some point timeout? or ? does the system hang locally, or
 remotely? (the latter can be explained)..
 
 Thanks.
 
 -- 
 /"\   Best regards,                      | remko@FreeBSD.org
 \ /   Remko Lodder                       | remko@EFnet
  X    http://www.evilcoder.org/          |
 / \   ASCII Ribbon Campaign              | Against HTML Mail and News
 
 

From: Yuri <yuri@tsoft.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/120636: Ndis driver causes system to hang while bringing
 AirLink101-AWLC3026 card up
Date: Tue, 26 Feb 2008 13:45:19 -0800

 There are numerous problems that I observe with this card.
 
 First some information.
 
 On the client host: when the driver loads in the presence of this card 
 dmesg is:
 ndis0: <Airlink101 802.11g Cardbus Adapter> mem 
 0x88000000-0x8800ffff,0x88010000-0x8801ffff irq 9 at device 0.0 on cardbus0
 ndis0: [ITHREAD]
 ndis0: NDIS API version: 5.1
 ndis0: using obsoleted if_watchdog interface
 ndis0: Ethernet address: 00:40:f4:e3:6b:4b
 
 On the AP side: FreeBSD access point is setup with the command:
 ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap 
 wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap
 
 On the AP side: 'ifconfig -v' prints:
 ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 00:18:f8:2e:40:25
         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
         media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
         status: associated
         ssid freebsdap channel 3 (2422 Mhz 11g) bssid 00:18:f8:2e:40:25
         authmode OPEN privacy ON deftxkey 3
         wepkey 1:104-bit
         wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpower 50
         txpowmax 50.0 rtsthreshold 2346 fragthreshold 2346 bmiss 7
         scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7
         roam:rate11a 12 roam:rssi11b 7 roam:rate11b 1 roam:rssi11g 7
         roam:rate11g 5 -pureg protmode CTS -ht -htcompat -ampdu 
 ampdulimit 8k
         ampdudensity - -amsdu -shortgi htprotmode RTSCTS -puren -wme -burst
         -ff -dturbo -hidessid apbridge dtimperiod 1 doth inact bintval 100
 
 On the client host: I set it up the card to connect to "freebsdap" network:
 ifconfig ndis0 ssid freebsdap wepmode on weptxkey 3 wepkey 
 3:0x3456789012 authmode open
 ifconfig ndis0 mode 11g
 ifconfig ndis0 inet 192.168.0.2 netmask 255.255.255.0
 ifconfig ndis0 up
 
 Card's transmit light blinks few times and stops. Based on lights it 
 looks like card is connected.
 
 On the client host: 'ifconfig -v' prints:
 ndis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 00:40:f4:e3:6b:4b
         inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
         media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (DS/1Mbps)
         status: associated
         ssid freebsdap channel 3 (2422 Mhz 11g) bssid 00:18:f8:2e:40:25
         authmode OPEN privacy OFF deftxkey 3
         wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpowmax 100
         rtsthreshold 2346 fragthreshold 2346 bmiss 7 mcastrate 1 
 scanvalid 60
         -bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 14 
 roam:rate11a 12
         roam:rssi11b 14 roam:rate11b 1 roam:rssi11g 14 roam:rate11g 5 -pureg
         protmode CTS -wme -burst -ff -dturbo roaming AUTO bintval 100
 
 
 PROBLEM#1: On the client host: when I try to ping AP (ping 192.168.0.1) 
 I get 100% packet loss.
 Transmit light doesn't blink in sync with ping.
 
 On the client host: I reset the card: 'ifconfig ndis0 down; ifconfig 
 ndis0 sid ""'.
 
 On the client side: 'ifconfig -v' prints:
 ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 00:40:f4:e3:6b:4b
         inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
         media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (DS/1Mbps)
         status: no carrier
         ssid "" channel 3 (2422 Mhz 11g) bssid 00:00:00:00:00:00
         authmode OPEN privacy OFF deftxkey 3
         wepkey 3:40-bit powersavemode OFF powersavesleep 100 txpowmax 100
         rtsthreshold 2346 fragthreshold 2346 bmiss 7 mcastrate 1 
 scanvalid 60
         -bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 14 
 roam:rate11a 12
         roam:rssi11b 14 roam:rate11b 1 roam:rssi11g 14 roam:rate11g 5 -pureg
         protmode CTS -wme -burst -ff -dturbo roaming AUTO bintval 100
 
 
 PROBLEM#2: On the client side: 'ifconfig ndis0 up scan' hangs. First 
 transmit light flashes
 few times but then command never returns and never prints anything.
 
 PROBLEM#3 (similar to PROBLEM#1): On the client host side: when I pull 
 the card out and put it back in and repeat the setup step (above)
 ping causes transmit light to flash in sync with ping few times and then 
 power light begins to flash for a while. And then power light stops 
 flashing.
 
 Also on the client host side every time when I ping AP dmesg gets:
 ndis0: link state changed to DOWN
 ndis0: link state changed to UP
 This seems very strange: why link state changes just because of ping?
 
 PROBLEM#4: I was also able to get kernel crash earlier. But I can;t 
 reproduce it now.
 I will append this PR when I am able to reproduce.
 
 PROBLEM#5: (from subject) I can't reproduce it now, but I will keep trying.
 
 Remko: please let me know if I can do something more to debug these 
 problems.
 

From: Yuri <yuri@tsoft.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/120636: Ndis driver causes system to hang while bringing
 AirLink101-AWLC3026 card up
Date: Wed, 27 Feb 2008 01:31:30 -0800

 After experimenting some more I get an impression that FreeBSD AP might 
 also be at fault.
 Since my Linux box which for some reason couldn't connect to this AP can 
 connect to the hardware WEP-AP.
 
 But AP setup nd client setup all followed Handbook steps.
 
 So there might be some bug in "ral" driver, or in the Handbook.
 

From: Volker <volker@vwsoft.com>
To: bug-followup@FreeBSD.org, yuri@tsoft.com
Cc:  
Subject: Re: kern/120636: Ndis driver causes system to hang while bringing
 AirLink101-AWLC3026 card up
Date: Fri, 29 Feb 2008 01:37:32 +0100

 Yuri,
 
 may I suggest not to key in every example command from the handbook and
 see how it fails? The handbook is really just to explain how things are
 working, not a "tell me 1:1 which commands I need to enter" tutorial and
 it's up to the user to configure everything to his needs.
 
 If you think documentation should be changed, you're free to join the
 docs team. I know they're happy for every helping hand to write the
 documentation.
 
 Anyway, to solve your problem, I'm really wondering if you're able to
 get your wifi network working when using either no wep key index number
 or at least start with number 1 index key?
 
 To start with wifi networks and figuring out how to configure them, it
 often helps to first start with unencrypted network configurations. If
 you have that running, you may just make the next step and enable WEP.
 
 If it doesn't work in the first step, please enable wlan debugging and
 see what you're getting. As you've been afraid to show us your dmesg or
 at least output of `uname -a', everything else is guesswork for us.
 
 Please notice, there have been wlan changes lately in the RELENG_7
 branch, so it may make sense to you to cvsup to the latest, rebuild
 kernel + world and retry setting up everything.
 
 Also keep in mind, wep "protected" networks are known to get broken
 easily for years and it's advised to use WPA instead. hostapd and
 wpa_supplicant will happily do their jobs and it's not too difficult to
 set them up under FreeBSD.
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Fri Feb 29 05:10:16 UTC 2008 
State-Changed-Why:  
Note that submitter has been asked for feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120636 
Responsible-Changed-From-To: freebsd-bugs->vwe 
Responsible-Changed-By: vwe 
Responsible-Changed-When: Tue Mar 11 02:35:29 UTC 2008 
Responsible-Changed-Why:  

track 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120636 
State-Changed-From-To: feedback->closed 
State-Changed-By: vwe 
State-Changed-When: Wed May 14 21:05:31 UTC 2008 
State-Changed-Why:  

We're sorry to not see any feedback received for quite some time. 
If you think this is still an issue that should be worked on, 
please provide the requested information and we'll be happy to 
re-open this ticket. 
Thank you for bringing this problem to attention! 

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