#942: immidiate disconnection on scan request (using wpa_supplicant)
----------------------------------+-----------------------------------------
      Reporter:  marek            |       Owner:     
          Type:  defect           |      Status:  new
      Priority:  major            |   Milestone:     
     Component:  madwifi: driver  |     Version:     
    Resolution:                   |    Keywords:     
Patch_attached:  0                |  
----------------------------------+-----------------------------------------
Comment (by Marek):

 Well, seem this issue doesnt want to let go...
 the setup worked for a week, then started to break again - i experience
 disconnections at various intervals. I have set up an open access AP with
 no daemon running:
 {{{
 iface ath0 inet static
         pre-up          wlanconfig ath0 create wlandev wifi0 wlanmode ap
         post-down       wlanconfig ath0 destroy
         address         10.0.1.1
         netmask         255.255.255.0
         wireless-mode   master
         wireless-channel 7
         wireless-essid  myssid
 }}}
 yet, when i try to connect to this AP with wpa_supplicant from another
 machine (both AP and client are using atheros/madwifi), i receive;
 {{{
 ...
 Wireless event: cmd=0x8b1a len=17
 Wireless event: cmd=0x8b15 len=20
 Wireless event: new AP: 00:0e:2e:90:50:34
 State: ASSOCIATING -> ASSOCIATED
 Associated to a new BSS: BSSID=00:0e:2e:90:50:34
 Associated with 00:0e:2e:90:50:34
 WPA: Association event - clear replay counter
 EAPOL: External notification - portEnabled=0
 EAPOL: External notification - portValid=0
 EAPOL: External notification - portEnabled=1
 EAPOL: SUPP_PAE entering state S_FORCE_AUTH
 EAPOL: SUPP_BE entering state IDLE
 Cancelling authentication timeout
 Removed BSSID 00:0e:2e:90:50:34 from blacklist
 State: ASSOCIATED -> COMPLETED
 CTRL-EVENT-CONNECTED - Connection to 00:0e:2e:90:50:34 completed (reauth)
 RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added

 <<< and then after some time... >>>

 Wireless event: cmd=0x8b15 len=20
 Wireless event: new AP: 00:00:00:00:00:00
 Setting scan request: 0 sec 100000 usec
 Added BSSID 00:0e:2e:90:50:34 into blacklist
 State: COMPLETED -> DISCONNECTED
 EAPOL: External notification - portEnabled=0
 EAPOL: SUPP_PAE entering state DISCONNECTED
 EAPOL: SUPP_BE entering state INITIALIZE
 EAPOL: External notification - portValid=0
 CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
 RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
 State: DISCONNECTED -> SCANNING
 }}}
 apparently it receives the new AP event with zeroed MAC (disconnection)
 but this must come from the madwifi driver, as like i said there is no
 daemon (like hostapd) running on the AP

 i have tried various snapshots of madwifi-ng on the AP (including todays),
 but with no luck.
 any thoughts about how to find out the core of the problem? For the start,
 how to find out if this is really AP sending disconnection event or
 somehow the client genrates it on its own?

 any help will be really aprreciated

-- 
Ticket URL: <http://madwifi.org/ticket/942>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to