|
好多年我都不知道光设置好如何测试11r是正常工作的,直到看了这个帖子https://www.reddit.com/r/openwrt ... =search&pto=aue 记得FQ。
转一段原文过来:
How do I know its working?
Actually doing
wpa_cli roam 11:22:33:44:55:01
never did a fast transition for me. I wasn't able to force an FT, so I had to walk around the house for tests.
On the OpenWRT/Lede node, the system log ("logread" on the console) will show:
Sun Sep 4 16:50:17 2016 daemon.debug hostapd: wlan0: STA 22:33:44:55:66:77 IEEE 802.11: authentication OK (FT)
Sun Sep 4 16:50:17 2016 daemon.debug hostapd: wlan0: STA 22:33:44:55:66:77 MLME: MLME-AUTHENTICATE.indication(22:33:44:55:66:77, FT)
Sun Sep 4 16:50:17 2016 daemon.debug hostapd: wlan0: STA 22:33:44:55:66:77 WPA: FT authentication already completed - do not start 4-way handshake
on a successfull roam. But the "daemon.debug hostapd" suggests this is because I changed the log output level to "debug" and compiled wpad with CONFIG_WPA_MSG_MIN_PRIORITY=1.
You can also sniff the wifi somehow and see if the 4-way handshake happens (bad) or not. But apart from that, I found no easy way to know if it worked or not.
debugging output from hostapd
I tried to experiment directly with the hostapd.conf and not use UCI at all. I did it like this on the console:
cd /tmp/run
cp hostapd-phy0.conf hostapd.conf
Then disable the wifi using LUCI, UCI or whatever you use and:
iw phy phy0 interface add wlan0 type managed
hostapd -P /var/run/hostapd-phy0.pid -dd hostapd.conf
The "-dd" option puts extra debugging output on the console. With this you can see directly if pmk_r1_push works. Since hostapd -dd is very verbose (with CONFIG_WPA_MSG_MIN_PRIORITY=1), you might want to add |grep FT to the hostapd command line.
|
|