[BUG] wpa_supplicant in SAE mode kills AP on same PHY
Charlemagne Lasse
charlemagnelasse at gmail.com
Thu Feb 23 06:13:36 PST 2017
Hi,
sorry for sending again but mailing list rejected last mail
I found a weird problem in LEDE 17.01 with an ath9k device and
reported it at https://bugs.lede-project.org/index.php?do=details&task_id=550
. But it looks like it is a bug in hostapd/wpa_supplicant because I
cannot reproduce it when using authsae.
Test setup is a bridge with two devices in it. One encrypted AP and
one encrypted mesh point. Both devices are using the same ath9k phy.
I did the tests with the attached files placed under /va/run/. The
following steps were done. Both hostapd and wpa_supplicant were run on
different terminals
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mkdir -p /var/run/hostapd/
iw phy phy0 interface add ap-2 type managed
ip link set address ac:86:74:00:00:01 dev ap-2
ip link set up dev ap-2
iw phy phy0 interface add mesh-2 type mp
ip link set address ae:86:74:00:00:01 dev mesh-2
ip link set up dev mesh-2
ip link add name br-lan type bridge
brctl addif br-lan mesh-2
ip link set br-lan up
/usr/sbin/hostapd -s -P /var/run/wifi-phy0.pid /var/run/hostapd-phy0.conf
/usr/sbin/wpa_supplicant -b br-lan -P
/var/run/wpa_supplicant-mesh-2.pid -D nl80211 -i mesh-2 -c
/var/run/wpa_supplicant-mesh-2.conf -C /var/run/wpa_supplicant -H
/var/run/hostapd/ap-2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The output of iw was following (and the AP didn't work):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
phy#0
Interface mesh-2
ifindex 7
wdev 0x3
addr ae:86:74:00:00:01
type mesh point
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
Interface ap-2
ifindex 6
wdev 0x2
addr ac:86:74:00:00:01
type AP
txpower 20.00 dBm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tested for a general driver problem by running the test again with
authsae as replacement for wpa_supplicant
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mkdir -p /var/run/hostapd/
iw phy phy0 interface add ap-2 type managed
ip link set address ac:86:74:00:00:01 dev ap-2
ip link set up dev ap-2
iw phy phy0 interface add mesh-2 type mp
ip link set address ae:86:74:00:00:01 dev mesh-2
ip link set up dev mesh-2
ip link add name br-lan type bridge
brctl addif br-lan mesh-2
ip link set br-lan up
/usr/sbin/hostapd -s -P /var/run/wifi-phy0.pid /var/run/hostapd-phy0.conf
/usr/bin/meshd-nl80211 -i mesh-2 -s mymesh -c /var/run/authsae-mesh-2.cfg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The AP works fine and the iw output is:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
phy#0
Interface mesh-2
ifindex 7
wdev 0x3
addr ae:86:74:00:00:01
type mesh point
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
Interface ap-2
ifindex 6
wdev 0x2
addr ac:86:74:00:00:01
ssid meshedAP
type AP
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I also tested if the AP works fine before starting wpa_supplicant.
This seems to be the case. It only breaks after starting the
wpa_supplicant.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: authsae-mesh-2.cfg
Type: application/octet-stream
Size: 361 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20170223/cb3c1627/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hostapd-phy0.conf
Type: application/octet-stream
Size: 415 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20170223/cb3c1627/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant-mesh-2.conf
Type: application/octet-stream
Size: 148 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20170223/cb3c1627/attachment-0002.obj>
More information about the Hostap
mailing list