Date: Mon, 6 Jul 2009 13:37:47 +0900 From: Weongyo Jeong <weongyo.jeong@gmail.com> To: Nikos Vassiliadis <nvass9573@gmx.com> Cc: freebsd-net@freebsd.org Subject: Re: ndis and USB wirelless ethernet Message-ID: <20090706043747.GD1138@weongyo.cdnetworks.kr> In-Reply-To: <4A4E2873.3010501@gmx.com> References: <4A43386D.80500@gmx.com> <20090625103420.GD31161@weongyo.cdnetworks.kr> <4A436A8A.1000405@gmx.com> <20090626041246.GE31161@weongyo.cdnetworks.kr> <4A461AF9.7040900@gmx.com> <20090629032520.GA1138@weongyo.cdnetworks.kr> <4A4880EF.5010206@gmx.com> <4A4E2873.3010501@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 03, 2009 at 06:49:07PM +0300, Nikos Vassiliadis wrote: > Hello Weongyo & net, > > I did some tests with an AP. The bad news is that I am > getting random crashes. At least I cannot relate them > to something... It just stops responding, I cannot break > to the debugger. Would I try another driver? there are > 3 versions if I recall correctly on the vendor's site. I'm happy to see your device is successfully associated with AP. However it seems it's a bad news that you sometimes meet crashes. Does a random crash mean a OS hang (e.g. could not type any keys) or no more work of network operations? Frankly speaking, for both cases it looks I could not provide any solutions without backtraces unless I encountered same problems on my environment. It'd better if we can reproduce its problem easily. One thing to hang as far as I know is that try to execute `ifconfig down && ifconfig up' multiple times. In NDIS USB support it's recommended that `ifconfig up' is executed once. I think you can try another drivers. > Something strange I've noticed, is that if I set the ssid > before setting the interface to "up" state, it does not > associate with the AP. > > ifconfig wlan0 down > ifconfig wlan0 ssid barba > ifconfig wlan0 up > > > Setting BSSID to 00:1b:2f:be:78:aa > > ndis_newstate: INIT -> SCAN > > ndis0: link state changed to DOWN > > ndis0: link state changed to UP > > ndis_scan_results: 4 results > > scan: bssid 00:1c:a2:b2:4e:e5 chan 2412MHz (1/1152) rssi 25 > > scan: bssid 00:13:33:07:90:90 chan 2442MHz (7/1152) rssi 75 > > scan: bssid 00:05:59:0a:b7:c1 chan 2437MHz (6/1152) rssi 60 > > scan: bssid 00:1a:4f:20:dc:4a chan 2437MHz (6/1152) rssi 6 > > wlan0: ieee80211_new_state_locked: pending SCAN -> RUN transition lost > > ndis_newstate: SCAN -> AUTH > > Setting BSSID to 00:1b:2f:be:78:aa > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "barba" > > ndis_newstate: AUTH -> ASSOC > > If if delete the ssid, and "up" the interface, it > associates: > > > Setting BSSID to 00:1b:2f:be:78:aa > > ndis_newstate: INIT -> SCAN > > ndis0: link state changed to DOWN > > ndis_scan_results: 4 results > > scan: bssid 00:13:33:07:90:90 chan 2442MHz (7/1152) rssi 73 > > scan: bssid 00:1c:a2:b2:4e:e5 chan 2412MHz (1/1152) rssi 15 > > scan: bssid 00:1a:4f:20:dc:4a chan 2437MHz (6/1152) rssi 7 > > scan: bssid 00:05:59:0a:b7:c1 chan 2437MHz (6/1152) rssi 54 > > ndis_newstate: SCAN -> AUTH > > Setting BSSID to 00:1b:2f:be:78:aa > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "barba" > > ndis_newstate: AUTH -> ASSOC > > ndis_newstate: ASSOC -> RUN > > ndis0: link state changed to UP > > If you have some idea, I would be happy to test it. AFAIK this behavior (ASSOC -> RUN) depends on the routine of the link status change on NDIS driver that in private experience, some drivers doesn't call the link status handler even if it's ready to use or call the handler too early which is one of the abnormal. So don't know what's going on in NDIS driver currently. regards, Weongyo Jeong
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090706043747.GD1138>