0
如果在開放模式下使用WEP安全性,那麼運行Linux內核的客戶端如何能夠檢查由於密鑰錯誤而導致的身份驗證失敗,但由於它是WEP開放模式。如何檢查Linux中的WEP身份驗證是否失敗
如果在開放模式下使用WEP安全性,那麼運行Linux內核的客戶端如何能夠檢查由於密鑰錯誤而導致的身份驗證失敗,但由於它是WEP開放模式。如何檢查Linux中的WEP身份驗證是否失敗
你會在wpa_supplican的日誌中看到這個。它看起來在某種程度上像這樣(對不起,只是隨便舉個例子我在網上查到):
[ 778.327092] wlan0: associated
[ 778.332503] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 788.334222] wlan0: disassociating from 00:1c:f0:b1:80:6a by local choice (reason=3)
[ 788.341433] cfg80211: Calling CRDA for country: US
[ 788.342348] wlan0: deauthenticating from 00:1c:f0:b1:80:6a by local choice (reason=3)
[ 789.122029] wlan0: no IPv6 routers present
[ 789.263341] wlan0: authenticate with 00:1c:f0:b1:80:6a (try 1)
[ 789.463049] wlan0: authenticate with 00:1c:f0:b1:80:6a (try 2)
[ 789.663048] wlan0: authenticate with 00:1c:f0:b1:80:6a (try 3)
[ 789.863057] wlan0: authentication with 00:1c:f0:b1:80:6a timed out
正如你可以從上面的日誌中看到,客戶端已成功關聯(778.327092),但未能在認證階段( 789.863057)。
您也可以使用* wpa_cli *和其「狀態」命令:
> status
bssid=00:1c:f0:b1:80:6a
ssid=KLUK2
id=1
mode=station
pairwise_cipher=NONE
group_cipher=NONE
key_mgmt=IEEE 802.1X (no WPA)
wpa_state=ASSOCIATED
Supplicant PAE state=CONNECTING
suppPortStatus=Unauthorized
EAP state=IDLE
<2>Authentication with 00:1c:f0:b1:80:6a timed out.
> <2>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
> <2>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
> <2>CTRL-EVENT-SCAN-RESULTS
> <2>Trying to authenticate with 00:1c:f0:b1:80:6a (SSID='KLUK2' freq=2437 MHz)
<2>CTRL-EVENT-SCAN-RESULTS
<2>CTRL-EVENT-BSS-REMOVED 0 00:1d:19:cd:43:a1
> <2>CTRL-EVENT-BSS-REMOVED 1 00:24:fe:82:ea:d9
> <2>CTRL-EVENT-BSS-REMOVED 2 00:04:0e:8e:a7:fe
> <2>CTRL-EVENT-SCAN-RESULTS
詳細信息多一點,你做什麼... – shkschneider
只是ping主機Ø試着接收一些數據。 –