On 5/26/19 1:24 PM, Peter Lundkvist wrote: > Hi, > > On 2019-05-05 23:43, Hauke Mehrtens wrote: >> On 5/5/19 6:59 AM, Stefan Lippers-Hollmann wrote: >>> Hi >>> >>> Successfully build-tested on: >>> - ath79 >>> - ipq806x >>> - lantiq >>> >>> Succeffully runtime tested on: >>> - ipq806x >>> >>> On 2019-05-04, Hauke Mehrtens wrote: >>>> This also syncs the configuration files with the default configuration >>>> files, but no extra options are activated or deactivated. >>>> >>>> The mesh patches were partially merged into hostapd 2.8, the remaining >>>> patches were extracted from patchwork and are now applied by OpenWrt. >>>> The patches still have open questions which are not fixed by the author. >>>> They were taken from this page: >>>> https://patchwork.ozlabs.org/project/hostap/list/?series=62725&state=* >>>> >>>> Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de> >>> Tested-by: Stefan Lippers-Hollmann <s.l-h at gmx.de> >>> >>> [...] >>>> --- a/package/network/services/hostapd/Makefile >>>> +++ b/package/network/services/hostapd/Makefile >>>> @@ -11,9 +11,9 @@ PKG_RELEASE:=6 >>>> >>>> PKG_SOURCE_URL:=http://w1.fi/hostap.git >>>> PKG_SOURCE_PROTO:=git >>>> -PKG_SOURCE_DATE:=2018-12-02 >>> [...] >>>> +PKG_SOURCE_DATE:=2.8 >>> [...] >>> >>> The version number goes backwards here, I'd suggest sticking to the >>> date here (2019-04-21) otherwise opkg would like to install the older >>> snapshot again: >>> >>> # opkg update >>> [...] >>> # opkg list-upgradable >>> hostapd-utils - 2.8-63962824-6 - 2018-12-02-c2c6c01b-6 >>> wpad-openssl - 2.8-63962824-6 - 2018-12-02-c2c6c01b-6 >>> wpa-cli - 2.8-63962824-6 - 2018-12-02-c2c6c01b-6 >>> hostapd-common - 2.8-63962824-6 - 2018-12-02-c2c6c01b-6 >>> >>> You might also want to reset PKG_RELEASE to 1: >>> >>> --- a/package/network/services/hostapd/Makefile >>> +++ b/package/network/services/hostapd/Makefile >>> @@ -7,11 +7,11 @@ >>> include $(TOPDIR)/rules.mk >>> >>> PKG_NAME:=hostapd >>> -PKG_RELEASE:=6 >>> +PKG_RELEASE:=1 >>> >>> PKG_SOURCE_URL:=http://w1.fi/hostap.git >>> PKG_SOURCE_PROTO:=git >>> -PKG_SOURCE_DATE:=2.8 >>> +PKG_SOURCE_DATE:=2019-04-21 >>> PKG_SOURCE_VERSION:=63962824309bb428e5f73d9caae08fcb949fbe36 >>> >>> PKG_MIRROR_HASH:=c3d789b822428c92bd47b3c85d9dc36cced38f7affe885cc2bb15e54248a4566 >> >> Ok, I will fix this. >> >> Thanks for testing. >> Did someone test the ieee80211s mesh functionality? > > I did some quick tests with mesh, and I see one regression when trying to set > up mesh on DFS channels (seems to work ok on non-DFS channels). > > With hostapd-2.8-63962824: > Sun May 26 10:23:09 2019 daemon.notice wpa_supplicant[18266]: mesh1: > interface state COUNTRY_UPDATE->DFS > Sun May 26 10:23:09 2019 daemon.notice wpa_supplicant[18266]: mesh1: > DFS-CAC-START freq=5680 chan=136 sec_chan=-1, width=0, seg0=0, seg1=0, > cac_time=60s > Sun May 26 10:23:10 2019 daemon.notice wpa_supplicant[18266]: mesh1: > MESH-GROUP-STARTED ssid="asdd390we12nwxx" id=0 > Sun May 26 10:24:10 2019 daemon.notice wpa_supplicant[18266]: mesh1: > DFS-CAC-COMPLETED success=1 freq=5680 ht_enabled=0 chan_offset=0 chan_width=0 > cf1=5680 cf2=0 > Sun May 26 10:24:12 2019 daemon.notice wpa_supplicant[18266]: mesh1: Unknown > event 54 > > With hostapd-2018-12-02-c2c6c01b: > Sun May 26 10:33:15 2019 daemon.notice wpa_supplicant[18709]: mesh1: > interface state COUNTRY_UPDATE->DFS > Sun May 26 10:33:15 2019 daemon.notice wpa_supplicant[18709]: mesh1: > DFS-CAC-START freq=5680 chan=136 sec_chan=-1, width=0, seg0=134, seg1=0, > cac_time=60s > Sun May 26 10:33:15 2019 daemon.notice wpa_supplicant[18709]: mesh1: > MESH-GROUP-STARTED ssid="asdd390we12nwxx" id=0 > Sun May 26 10:34:19 2019 daemon.notice wpa_supplicant[18709]: mesh1: > DFS-CAC-COMPLETED success=1 freq=5680 ht_enabled=1 chan_offset=-1 > chan_width=2 cf1=5670 cf2=0 > Sun May 26 10:34:19 2019 daemon.err wpa_supplicant[18709]: Using interface > mesh1 with hwaddr ba:ec:a3:d7:6a:c1 and ssid "" > Sun May 26 10:34:19 2019 daemon.notice wpa_supplicant[18709]: mesh1: > interface state DFS->ENABLED > Sun May 26 10:34:19 2019 daemon.notice wpa_supplicant[18709]: mesh1: > AP-ENABLED > > /Peter >
Hi Peter, Thanks for reporting this. Event 54 is EVENT_DFS_PRE_CAC_EXPIRED There are two places which print out "Unknown event", I assume you hit the version in ./wpa_supplicant/events.c because of the debug level. In this switch statement EVENT_DFS_PRE_CAC_EXPIRED is not handled, so we should see this message in case the code receives this event. I am not familiar with the hostapd code, but I would suggest to handle the event like it is done in ./src/ap/drv_callbacks.c by calling a local function and then the existing function hostapd_dfs_pre_cac_expired(). Hauke _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel