From owner-freebsd-net@FreeBSD.ORG Fri Jul 3 15:49:38 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FEAF1065674 for ; Fri, 3 Jul 2009 15:49:38 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 2EDDB8FC21 for ; Fri, 3 Jul 2009 15:49:37 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: (qmail invoked by alias); 03 Jul 2009 15:49:35 -0000 Received: from ipa71.5.107.79.tellas.gr (EHLO [169.254.0.2]) [79.107.5.71] by mail.gmx.com (mp-eu001) with SMTP; 03 Jul 2009 17:49:35 +0200 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1/iO9sT+tji42r/NI/HwGpIf5fm3viPXr4wl1PrhN cM1WSCzmP+mjFl Message-ID: <4A4E2873.3010501@gmx.com> Date: Fri, 03 Jul 2009 18:49:07 +0300 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Nikos Vassiliadis , weongyo@freebsd.org 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> In-Reply-To: <4A4880EF.5010206@gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.5600000000000001 Cc: freebsd-net@freebsd.org Subject: Re: ndis and USB wirelless ethernet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 15:49:38 -0000 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. 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. Thanks, Nikos