Hi Max, It works. Attached is the successfull log from wpa_supplicant.
Thanks for the quick response. /glz--On Tuesday, October 10, 2006 05:04:46 +0200 Max Laier <[EMAIL PROTECTED]> wrote:
On Monday 09 October 2006 20:26, Max Laier wrote:On Monday 09 October 2006 19:53, Andrew N. Below wrote: > Hi. > > [..] > > > You can try using ap_scan=2 or whatever it is in the > > wpa_supplicant.conf file. This causes wpa_supplicant to use > > directed broadcasts msgs to each ap listed in the file. > > In my case setting ap_scan to 2 doesn't help. > > BTW, I got successfull connection some time ago when I > start to use /etc/rc.d/netif start iwi0 instead of manual > running of wpa_supplicant: > > defanbook# ifconfig iwi0 > iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 213.189.198.75 netmask 0xfffffff0 broadcast > 213.189.198.79 ether 00:12:f0:3d:cd:58 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > (DS/11Mbps) status: associated > ssid ZENON-RADIO channel 11 bssid 00:07:0e:b8:d8:ee > authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP > 3:128-bit txpowmax 100 bmiss 10 protmode CTS roaming MANUAL bintval > 100 > > I wrote bssid value to /etc/wpa_supplicant.conf and run > /etc/rc.d/netif. > > Then I drop connection (netif stop iwi0) and tried to start it again. > I got "associated" state in 5-6 minutes. > > In rc.conf I have: > > ifconfig_iwi0="ssid MY-SSID channel 11 WPA > > How can I get "-dd" output from wpa_supplicant started with netif? > It could be interesting. No idea, but a bit more stress testing did reveal a similar problem here. After I associated with the AP w/ hidden SSID I changed the channel via webinterface. The disconnect resulted in the exact problem you were having. Only stopping and restarting wpa_supplicant fixed the issue and I got associated on the new channel. Not sure what happens there yet, but something seems to get stuck in an undefined state.Could you try the attached - untested - patch? It seems - from looking at the linux driver - that we have to remind the firmware of the ESSID before doing a directed scan. That explains why it would sometimes work (whenever we are coming straight from iwi_config) and sometimes not. Let me know if that improves things for you. Thanks. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News
-- ................................................... the future isMobile Goran Lowkrantz <[EMAIL PROTECTED]> System Architect, isMobile, Aurorum 2, S-977 75 Lule￥, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ...............................................
iwipatch.log
Description: Binary data
_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
