Re: trouble with hostapd
On 06.08.23 17:29, e9hack wrote: Am 04.08.2023 um 13:01 schrieb Felix Fietkau: Can you please build hostapd with CONFIG_WPA_MSG_MIN_PRIORITY=0 in the OpenWrt .config, add -d to the hostapd command in /etc/init.d/wpad Afterwards, please show me the relevant log part with the full context of the beacon command, so that I can figure out which parameter might be going out of range. It occurs again after restarting of hostapd: Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: beacon_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: proberesp_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: assocresp_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: he_spr_ctrl=0x3 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * freq=2462 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * eht_enabled=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * he_enabled=1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * vht_enabled=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * ht_enabled=1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * radar_background=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * sec_channel_offset=-1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * channel_type=2 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: twt_responder=1 Sun Aug 6 12:46:39 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Beacon set failed: -34 (Result not representable) Sun Aug 6 12:46:39 2023 daemon.err hostapd: Failed to set beacon parameters Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Fetch survey data Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Freq survey dump event (freq=2462 MHz noise=0 channel_time=71621861 busy_time=7745546 tx_time=2674494 rx_time=4839616 filled=001e) I send a bigger log from the 90 sec before off-list. After trying many different things, I finally figured out that it was related to BSS color collisions, and only when using multiple interfaces on the same PHY. Fixed in latest master. Thanks for reporting this, - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: trouble with hostapd
Am 04.08.2023 um 13:01 schrieb Felix Fietkau: Can you please build hostapd with CONFIG_WPA_MSG_MIN_PRIORITY=0 in the OpenWrt .config, add -d to the hostapd command in /etc/init.d/wpad Afterwards, please show me the relevant log part with the full context of the beacon command, so that I can figure out which parameter might be going out of range. It occurs again after restarting of hostapd: Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: beacon_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: proberesp_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: assocresp_ies - hexdump(len=12): 7f 0a 04 00 00 00 01 00 01 40 00 40 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: he_spr_ctrl=0x3 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * freq=2462 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * eht_enabled=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * he_enabled=1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * vht_enabled=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * ht_enabled=1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * radar_background=0 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * sec_channel_offset=-1 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: * channel_type=2 Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: twt_responder=1 Sun Aug 6 12:46:39 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Beacon set failed: -34 (Result not representable) Sun Aug 6 12:46:39 2023 daemon.err hostapd: Failed to set beacon parameters Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Fetch survey data Sun Aug 6 12:46:39 2023 daemon.debug hostapd: nl80211: Freq survey dump event (freq=2462 MHz noise=0 channel_time=71621861 busy_time=7745546 tx_time=2674494 rx_time=4839616 filled=001e) I send a bigger log from the 90 sec before off-list. Regards, Hartmut ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: trouble with hostapd
On 03.08.23 20:17, e9hack wrote: Am 03.08.2023 um 18:51 schrieb Felix Fietkau: On 03.08.23 15:34, e9hack wrote: Am 03.08.2023 um 14:35 schrieb Felix Fietkau: thanks for reporting this. Unfortunately I can't reproduce it myself based on your description. Can you please let me know what device you are using, and send me the config that reproduces this issue? I'm using an ASUS RT-AX53U. Hostapd has the radius server compiled in. Fixed in b8be20c7e81de2894df8fa2b361c39bc723e4cb5, thanks. This does fix the issue, thanks! Now I see some errors, which I've never seen before: Thu Aug 3 19:59:19 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:24 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:24 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:25 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:35 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:36 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:47 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:03:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Can you please build hostapd with CONFIG_WPA_MSG_MIN_PRIORITY=0 in the OpenWrt .config, add -d to the hostapd command in /etc/init.d/wpad Afterwards, please show me the relevant log part with the full context of the beacon command, so that I can figure out which parameter might be going out of range. Thanks, - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: trouble with hostapd
Am 03.08.2023 um 18:51 schrieb Felix Fietkau: On 03.08.23 15:34, e9hack wrote: Am 03.08.2023 um 14:35 schrieb Felix Fietkau: thanks for reporting this. Unfortunately I can't reproduce it myself based on your description. Can you please let me know what device you are using, and send me the config that reproduces this issue? I'm using an ASUS RT-AX53U. Hostapd has the radius server compiled in. Fixed in b8be20c7e81de2894df8fa2b361c39bc723e4cb5, thanks. This does fix the issue, thanks! Now I see some errors, which I've never seen before: Thu Aug 3 19:59:19 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:23 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:24 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 19:59:24 2023 daemon.err hostapd: Failed to set beacon parameters Thu Aug 3 19:59:25 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:35 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:36 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:00:47 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Thu Aug 3 20:03:23 2023 daemon.err hostapd: nl80211: kernel reports: integer out of range Regards, Hartmut ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: trouble with hostapd
On 03.08.23 15:34, e9hack wrote: Am 03.08.2023 um 14:35 schrieb Felix Fietkau: thanks for reporting this. Unfortunately I can't reproduce it myself based on your description. Can you please let me know what device you are using, and send me the config that reproduces this issue? I'm using an ASUS RT-AX53U. Hostapd has the radius server compiled in. Fixed in b8be20c7e81de2894df8fa2b361c39bc723e4cb5, thanks. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: trouble with hostapd
Hi, On 03.08.23 11:17, e9hack wrote: I've trouble with 5GHz since the last changes related to hostapd. After boot or after a sequence 'wifi down; sleep 30; wifi' the 2GHz starts only. The 5GHz doesn't start. It looks like, that ACS isn't started. If I modify a value in the config related to 5GHz and execute 'wifi reload', sometimes 5GHz starts. If I remove ACS and set a fixed channel, 5GHz starts only, if the channel doesn't need DFS because DFS is never finished successful. If I revert mac80211.sh and hostapd.sh back to the older versions, ACS and fixed channel with DFS does work again. thanks for reporting this. Unfortunately I can't reproduce it myself based on your description. Can you please let me know what device you are using, and send me the config that reproduces this issue? Thanks, - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
trouble with hostapd
I've trouble with 5GHz since the last changes related to hostapd. After boot or after a sequence 'wifi down; sleep 30; wifi' the 2GHz starts only. The 5GHz doesn't start. It looks like, that ACS isn't started. If I modify a value in the config related to 5GHz and execute 'wifi reload', sometimes 5GHz starts. If I remove ACS and set a fixed channel, 5GHz starts only, if the channel doesn't need DFS because DFS is never finished successful. If I revert mac80211.sh and hostapd.sh back to the older versions, ACS and fixed channel with DFS does work again. Regards, Hartmut ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
