Re: wpa_supplicant: secured mesh and WiLink8 issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



   Hi Bob,

I tried your advice in
https://bobcopeland.com/blog/2016/10/encrypted-mesh-psa/ . I am using
a 3.4 kernel and trying out wpa_supplicant 2.6, so I added
ieee80211w=2 to the configuration:

%< snip >%
user_mpm=1
update_config=1

network={
        mode=5
        ssid="secret"
        frequency=2412
        proto=RSN
        pairwise=CCMP
        key_mgmt=SAE
        group=CCMP
        psk="secret"
}
%< snip >%

The first mesh node that went up initially showed this:

2016-11-04T12:33:02.729432+00:00 AirFi wpa_supplicant[472]:
Successfully initialized wpa_supplicant
2016-11-04T12:33:02.804144+00:00 AirFi wpa_supplicant[472]: rfkill:
Cannot open RFKILL control device
2016-11-04T12:33:02.807048+00:00 AirFi wpa_supplicant[472]: nl80211:
Could not re-add multicast membership for vendor events: -2 (No such
file or directory)
2016-11-04T12:33:04.664526+00:00 AirFi wpa_supplicant[476]: wlan1:
CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
2016-11-04T12:33:04.665503+00:00 AirFi wpa_supplicant[476]: wlan1:
CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
2016-11-04T12:33:06.983435+00:00 AirFi wpa_supplicant[476]: Using
interface wlan1 with hwaddr xx:xx:xx:xx:xx:52 and ssid ""
2016-11-04T12:33:06.987025+00:00 AirFi wpa_supplicant[476]: wlan1:
interface state UNINITIALIZED->ENABLED
2016-11-04T12:33:06.987105+00:00 AirFi wpa_supplicant[476]: AP-ENABLED
2016-11-04T12:33:07.004874+00:00 AirFi wpa_supplicant[476]: wlan1:
joining mesh "<secret>"
2016-11-04T12:33:07.006015+00:00 AirFi wpa_supplicant[476]: wlan1:
mesh join error=-114
2016-11-04T12:33:07.006674+00:00 AirFi wpa_supplicant[476]: wlan1:
Could not join mesh
2016-11-04T12:36:58.862178+00:00 AirFi wpa_supplicant[476]: wlan1:
MESH-GROUP-REMOVED wlan1
2016-11-04T12:36:58.862298+00:00 AirFi wpa_supplicant[476]: wlan1: leaving mesh
2016-11-04T12:36:58.862467+00:00 AirFi wpa_supplicant[476]: wlan1:
interface state ENABLED->DISABLED
2016-11-04T12:36:58.871443+00:00 AirFi wpa_supplicant[476]: AP-DISABLED
2016-11-04T12:36:59.397112+00:00 AirFi wpa_supplicant[476]: nl80211:
Failed to open /proc/sys/net/ipv4/conf/wlan1/drop_unicast_in_l2_multicast:
No such file or directory
2016-11-04T12:36:59.397807+00:00 AirFi wpa_supplicant[476]: nl80211:
Failed to set IPv4 unicast in multicast filter
2016-11-04T12:36:59.402978+00:00 AirFi wpa_supplicant[476]: nl80211:
Failed to open /proc/sys/net/ipv4/conf/wlan1/drop_unicast_in_l2_multicast:
No such file or directory
2016-11-04T12:36:59.403550+00:00 AirFi wpa_supplicant[476]: nl80211:
Failed to set IPv4 unicast in multicast filter
2016-11-04T12:36:59.404538+00:00 AirFi wpa_supplicant[476]: nl80211:
deinit ifname=wlan1 disabled_11b_rates=0

After restarting wpa_supplicant (with two other nodes running already)
I instead got this:

2016-11-04T12:40:17.549010+00:00 AirFi wpa_supplicant[1018]:
Successfully initialized wpa_supplicant
2016-11-04T12:40:17.716374+00:00 AirFi wpa_supplicant[1018]: rfkill:
Cannot open RFKILL control device
2016-11-04T12:40:17.718967+00:00 AirFi wpa_supplicant[1018]: nl80211:
Could not re-add multicast membership for vendor events: -2 (No such
file or directory)
2016-11-04T12:40:21.911925+00:00 AirFi wpa_supplicant[1019]: Could not
connect to kernel driver
2016-11-04T12:40:21.912717+00:00 AirFi wpa_supplicant[1019]: Using
interface wlan1 with hwaddr xx:xx:xx:xx:xx:52 and ssid ""
2016-11-04T12:40:21.913104+00:00 AirFi wpa_supplicant[1019]: wlan1:
interface state UNINITIALIZED->ENABLED
2016-11-04T12:40:21.913157+00:00 AirFi wpa_supplicant[1019]: AP-ENABLED
2016-11-04T12:40:22.415168+00:00 AirFi wpa_supplicant[1019]: wlan1:
joining mesh "<secret>"
2016-11-04T12:40:22.419532+00:00 AirFi wpa_supplicant[1019]: wlan1:
CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0
id_str=]
2016-11-04T12:40:22.419740+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-GROUP-STARTED ssid="<secret>" id=0
2016-11-04T12:40:22.923110+00:00 AirFi wpa_supplicant[1019]: wlan1:
new peer notification for xx:xx:xx:xx:xx:55
2016-11-04T12:40:23.438482+00:00 AirFi wpa_supplicant[1019]: wlan1:
new peer notification for xx:xx:xx:xx:xx:6c
2016-11-04T12:40:36.131965+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:55
2016-11-04T12:40:39.639177+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:6c
2016-11-04T12:40:53.579341+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:55
2016-11-04T12:40:54.826637+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:6c
2016-11-04T12:41:06.978773+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:55
2016-11-04T12:41:10.247987+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:6c
2016-11-04T12:41:22.687123+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:6c
2016-11-04T12:41:22.687351+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-BLOCKED addr=xx:xx:xx:xx:xx:6c duration=300
2016-11-04T12:41:23.169525+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-FAILURE addr=xx:xx:xx:xx:xx:55
2016-11-04T12:41:23.169756+00:00 AirFi wpa_supplicant[1019]: wlan1:
MESH-SAE-AUTH-BLOCKED addr=xx:xx:xx:xx:xx:55 duration=300

So maybe your advice needs some extra good bits for specific situations.

Kind regards,
    jer

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux