android wifi断开原因分析 |
您所在的位置：网站首页 › wifi总是断开的原因 › android wifi断开原因分析 |
|
1 在ASSOCIATING阶段由于丢包导致ASSOC REJECT
D/WifiMonitor( 924): Event [IFNAME=wlan0 CTRL-EVENT-DISCONNECTED bssid=08:cc:68:9e:ac:20 reason=3 locally_generated=1] I/wpa_supplicant(23065): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=0e:bd:51:c7:b6:33 status_code=1 2 在4WAY_HANDSHAKE阶段由于密码错误、丢帧或者弱信号丢包导致WRONG_KEY：密码错误在4WAY_HANDSHAKE阶段中的2/4次握手会显示wrong key。 如果已经连接过则显示 I/wpa_supplicant(19043): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="Onetouch Idol 3 (4.7)" auth_failures=1 duration=5 reason=WRONG_KEY。 丢帧导致连接断开： wlan: [24597:E :PE ] limHandleMissedBeaconInd: 2121: Sending EXIT_BMPS_IND to SME due to Missed beacon from FW 信号弱导致断开： I/wpa_supplicant(31023): wlan0: CTRL-EVENT-DISCONNECTED bssid=c8:3a:35:2b:71:30 reason=0 E/WifiStateMachine( 821): NETWORK_DISCONNECTION_EVENT in connected state BSSID=c8:3a:35:2b:71:30 RSSI=-89 freq=2437 was debouncing=false reason=0 ajst=0 reason=0表示因为信号弱而断开。 3 4WAY_HANDSHAK成功但DHCP FAILURE四步握手成功但获取IP地址失败 E/WifiStateMachine(28360): WifiStateMachine DHCP failure count=0 E/WifiConfigStore(28360): message=DHCP FAILURE 4 被AP踢出，这个原因需要sniffer log分析reason=2，reason=7，reason=15代表被AP踢出，在kernel log中可以找到对应的deauth信息。 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-DISCONNECTED bssid=c4:14:3c:29:47:05 reason=7 wlan: [28055:E :PE ] limProcessDeauthFrame: 144: Received Deauth frame for Addr: 44:a4:2d:52:bc:a5 (mlm state = eLIM_MLM_LINK_ESTABLISHED_STATE, sme state = 12 systemrole = 3) with reason code 7 from c4:14:3c:29:47:05 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-DISCONNECTED bssid=1c:1d:86:e9:e2:85 reason=15 wlan: [28055:E :PE ] limProcessDeauthFrame: 144: Received Deauth frame for Addr: 44:a4:2d:52:bc:a5 (mlm state = eLIM_MLM_LINK_ESTABLISHED_STATE, sme state = 12 systemrole = 3) with reason code 15 from 1c:1d:86:e9:e2:85 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-DISCONNECTED bssid=c4:14:3c:29:47:25 reason=2 wlan: [28055:E :PE ] limProcessDeauthFrame: 144: Received Deauth frame for Addr: 44:a4:2d:52:bc:a5 (mlm state = eLIM_MLM_LINK_ESTABLISHED_STATE, sme state = 12 systemrole = 3) with reason code 2 from c4:14:3c:29:47:25 5 在信号相差5-10rssi的时候会发生roam，roam是在firmware层发生的，不会断开。I/WifiHAL (28360): event received NL80211_CMD_ROAM, vendor_id = 0x0 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-CONNECTED - Connection to c4:14:3c:29:47:25 completed [id=0 id_str=] I/WifiHAL (28360): event received NL80211_CMD_ROAM, vendor_id = 0x0 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-CONNECTED - Connection to c4:14:3c:29:47:05 completed [id=0 id_str=] I/WifiHAL (28360): event received NL80211_CMD_ROAM, vendor_id = 0x0 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-CONNECTED - Connection to 1c:1d:86:e9:e2:85 completed [id=0 id_str=] 6 在打开auoto join的情况下，也会发生roam，也不会断开E/WifiStateMachine(28360): WifiStateMachine shouldSwitchNetwork txSuccessRate=0.00 rxSuccessRate=0.00 delta 1000 -> 1000 I/wpa_supplicant(28064): wlan0: CTRL-EVENT-CONNECTED - Connection to 6c:99:89:b0:01:85 completed [id=0 id_str=] I/wpa_supplicant(28064): wlan0: CTRL-EVENT-DISCONNECTED bssid=6c:99:89:b0:01:85 reason=0 E/WifiStateMachine(28360): WifiStateMachine shouldSwitchNetwork txSuccessRate=0.00 rxSuccessRate=0.00 delta 1000 -> 1000 7 802.11 Association Status Codes Code 802.11definitionExplanation0Successful1Unspecified failureFor example : when there is no ssid specified in an association request10Cannot support all requested capabilities in the Capability Information fieldExample Test: Reject when privacy bit is set for WLAN not requiring security11Reassociation denied due to inability to confirm that association existsNOT SUPPORTED12Association denied due to reason outside the scope of this standardExample : When controller receives assoc from an unknown or disabled SSID13Responding station does not support the specified authentication algorithmFor example, MFP is disabled but was requested by the client.14Received an Authentication frame with authentication transaction sequence number out of expected sequenceIf the authentication sequence number is not correct.15Authentication rejected because of challenge failure16Authentication rejected due to timeout waiting for next frame in sequence17Association denied because AP is unable to handle additional associated stationsWill happen if you run out of AIDs on the AP; so try associating a large number of stations.18Association denied due to requesting station not supporting all of the data rates in the BSSBasicRateSet parameterWill happen if the rates in the assoc request are not in the BasicRateSet in the beacon.19Association denied due to requesting station not supporting the short preamble optionNOT SUPPORTED20Association denied due to requesting station not supporting the PBCC modulationoptionNOT SUPPORTED21Association denied due to requesting station not supporting the Channel Agility optionNOT SUPPORTED22Association request rejected because Spectrum Management capability is requiredNOT SUPPORTED23Association request rejected because the information in the Power Capability element is unacceptableNOT SUPPORTED24Association request rejected because the information in the Supported Channels element is unacceptableNOT SUPPORTED25Association denied due to requesting station not supporting the Short Slot Time optionNOT SUPPORTED26Association denied due to requesting station not supporting the DSSS-OFDM optionNOT SUPPORTED27-31ReservedNOT SUPPORTED32Unspecified, QoS-related failureNOT SUPPORTED33Association denied because QAP has insufficient bandwidth to handle another QSTANOT SUPPORTED34Association denied due to excessive frame loss rates and/or poor conditions on current operating channelNOT SUPPORTED35Association (with QBSS) denied because the requesting STA does not support the QoS facilityIf the WMM is required by the WLAN and the client is not capable of it, the association will get rejected.36Reserved in 802.11This is used in our code ! There is no blackbox test for this status code.37The request has been declinedThis is not used in assoc response; ignore38The request has not been successful as one or more parameters have invalid valuesNOT SUPPORTED39The TS has not been created because the request cannot be honored; however, a suggested TSPEC is provided so that the initiating QSTA may attempt to set another TS with the suggested changes to the TSPECNOT SUPPORTED40Invalid information element, i.e., an information element defined in this standard for which the content does not meet the specifications in Clause 7Sent when Aironet IE is not present for a CKIP WLAN41Invalid group cipherUsed when received unsupported Multicast 802.11i OUI Code42Invalid pairwise cipher43Invalid AKMP44Unsupported RSN information element versionIf you put anything but version value of 1, you will see this code.45Invalid RSN information element capabilitiesIf WPA/RSN IE is malformed, such as incorrect length etc, you will see this code.46Cipher suite rejected because of security policyNOT SUPPORTED47The TS has not been created; however, the HC may be capable of creating a TS, in response to a request, after the time indicated in the TS Delay elementNOT SUPPORTED48Direct link is not allowed in the BSS by policyNOT SUPPORTED49Destination STA is not present within this QBSSNOT SUPPORTED50The Destination STA is not a QSTANOT SUPPORTED51Association denied because the ListenInterval is too largeNOT SUPPORTED200(0xC8)Unspecified, QoS-related failure. Not defined in IEEE, defined in CCXv4Unspecified QoS Failure. This will happen if the Assoc request contains more than one TSPEC for the same AC.201(0xC9)TSPEC request refused due to AP’s policy configuration (e.g., AP is configured to deny all TSPEC requests on this SSID). A TSPEC will not be suggested by the AP for this reason code. Not defined in IEEE, defined in CCXv4This will happen if a TSPEC comes to a WLAN which has lower priority than the WLAN priority settings. For example a Voice TSPEC coming to a Silver WLAN. Only applies to CCXv4 clients.202(0xCA)Association Denied due to AP having insufficient bandwidth to handle a new TS. This cause code will be useful while roaming only. Not defined in IEEE, defined in CCXv4203(0xCB)Invalid Parameters. The request has not been successful as one or more TSPEC parameters in the request have invalid values. A TSPEC SHALL be present in the response as a suggestion. Not defined in IEEE, defined in CCXv4This happens in cases such as PHY rate mismatch. If the TSRS IE contains a phy rate not supported by the controller, for example. Other examples include sending a TSPEC with bad parameters, such as sending a date rate of 85K for a narrowband TSPEC. 802.11 Deauth Reason CodesWhen running a client debug, this code will match the ReasonCode from the output: "Scheduling mobile for deletion with delete Reason x, reasonCode y" Code802.11 definitionExplanation0ReservedNOT SUPPORTED1Unspecified reasonTBD2Previous authentication no longer validNOT SUPPORTED3station is leaving (or has left) IBSS or ESSNOT SUPPORTED4Disassociated due to inactivityDo not send any data after association;5Disassociated because AP is unable to handle all currently associated stationsTBD6Class 2 frame received from nonauthenticated stationNOT SUPPORTED7Class 3 frame received from nonassociated stationNOT SUPPORTED8Disassociated because sending station is leaving (or has left) BSSTBD9Station requesting (re)association is not authenticated with responding stationNOT SUPPORTED10Disassociated because the information in the Power Capability element is unacceptableNOT SUPPORTED11Disassociated because the information in the Supported Channels element is unacceptableNOT SUPPORTED12ReservedNOT SUPPORTED13Invalid information element, i.e., an information element defined in this standard for which the content does not meet the specifications in Clause 7NOT SUPPORTED14Message integrity code (MIC) failureNOT SUPPORTED154-Way Handshake timeoutNOT SUPPORTED16Group Key Handshake timeoutNOT SUPPORTED17Information element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frameNOT SUPPORTED18Invalid group cipherNOT SUPPORTED19Invalid pairwise cipherNOT SUPPORTED20Invalid AKMPNOT SUPPORTED21Unsupported RSN information element versionNOT SUPPORTED22Invalid RSN information element capabilitiesNOT SUPPORTED23IEEE 802.1X authentication failedNOT SUPPORTED24Cipher suite rejected because of the security policyNOT SUPPORTED25-31ReservedNOT SUPPORTED32Disassociated for unspecified, QoS-related reasonNOT SUPPORTED33Disassociated because QAP lacks sufficient bandwidth for this QSTANOT SUPPORTED34Disassociated because excessive number of frames need to be acknowledged, but are not acknowledged due to AP transmissions and/or poor channel conditionsNOT SUPPORTED35Disassociated because QSTA is transmitting outside the limits of its TXOPsNOT SUPPORTED36Requested from peer QSTA as the QSTA is leaving the QBSS (or resetting)NOT SUPPORTED37Requested from peer QSTA as it does not want to use the mechanismNOT SUPPORTED38Requested from peer QSTA as the QSTA received frames using the mechanism for which a setup is requiredNOT SUPPORTED39Requested from peer QSTA due to timeoutNOT SUPPORTED40Peer QSTA does not support the requested cipher suiteNOT SUPPORTED46-6553546--65 535 ReservedNOT SUPPORTED98Cisco definedTBD99Cisco defined Used when the reason code sent in a deassoc req or deauth by the client is invalid – invalid length, invalid value etcExample: Send a Deauth to the AP with the reason code to be invalid, say zero作者：ylliu3788 链接：https://www.jianshu.com/p/285806063f13 来源：简书 著作权归作者所有。商业转载请联系作者获得授权，非商业转载请注明出处。 |
今日新闻 |
点击排行 |
|
推荐新闻 |
图片新闻 |
|
专题文章 |
| CopyRight 2018-2019 实验室设备网 版权所有 win10的实时保护怎么永久关闭 |