It's been three months since the last 23.05 release. Will there be a 23.05.3 release soon before the 24.xx release?
It seems reasonable to expect 23.05.3 soon, and you'll have several other minor releases before 24.xx is even branched.
1 Like
For non-developers, is there any good way to know if there have been any significant security/vulnerability patches since the last "stable" release?
I don't see any CVE's from 2023/2024 on the "Security" page, but for example, I know there was a recent SSH patch and the related CVE is not on that list, so I don't know how meaningful the list is.
List of commits for 23.05 here
You may also consider update of several packages since latest release.
In general, when significant security/ vulnerability issues are found and patched, the team makes a new stable release.
4 Likes
You can also sign up for emails (except the adm group, obviously) here: https://lists.openwrt.org/mailman/listinfo
2 Likes
Thank you.
1 Like
Hello, at this meeting it was said that version 23.05.3 would be released in two weeks, it was planned, did something happen that they couldn't release?
Best would probably be to ask from the actual developers who were in the meeting, like @hauke @daniel @jow , if there are updated plans for 23.05.3.
From device support perspective, 23.05.3 would bring MT6000 into "supported in release" category, making that new popular device hopefully acceptable even for @richb-hanover-priv who was strictly listing newcomer devices that are supported by a real release.
3 Likes
This is exactly my router and today I'm using 23.05-snapshot due to the lack of a stable one. I think the snapshot is very experimental and constantly updating it I don't think is a good idea.
Newest 23.05-snapshot of that moment would actually be practically identical to the forthcoming 23.05.3, as releases are simply tagged from the same 23.05 branch. There should be nothing really experimental in 23.05.
(Main/master snapshots are then a totally different beast.)
4 Likes
Is there any way that we could get "release"-snapshots (i.e. 23.05-snapshot) available in the Firmware Selector? That seems like a strange oversight.
There were available years ago, I can't remember when they were removed. You can still download the image builder and try your own.
https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/
1 Like
That was what I was hoping to avoid. The Firmware Selector is much more convenient in not requiring anything to be installed locally, etc. Just browse to the page, add packages, and download.
No big deal, I'd just consider it a wishlist item.
1 Like
auc supports updates on branch snapshot, and since it uses the same backend as the firmware selector (the ASU server api), it should work just fine. If you were to be explicit about it, you'd say
$ auc -b 23.05 -B 23.05-SNAPSHOT
but since you are already running the snapshot, it should default to that.
23.05.3 has been git tagged a few hours ago, but the build process and release process will likely take some 2-3 days before the release is properly released and announced.
3 Likes
I may have hit a regression in 23.05.3. Hostapd refuses to start correctly complaining about unknown configuration items wnm_sleep_mode, wnm_sleep_mode_no_keys and bss_transition. Is this a know issue?
Log
Fri Mar 22 23:10:09 2024 daemon.notice hostapd: Set new config for phy phy0:
Fri Mar 22 23:10:09 2024 daemon.notice hostapd: Set new config for phy phy1:
Fri Mar 22 23:10:10 2024 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Fri Mar 22 23:10:10 2024 daemon.notice hostapd: Restart interface for phy phy0
Fri Mar 22 23:10:10 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=DE ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 chanlist=13 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40-][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=8 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_vi_ecwmax=7 he_mu_edca_ac_
Fri Mar 22 23:10:10 2024 daemon.err hostapd: Line 80: unknown configuration item 'wnm_sleep_mode'
Fri Mar 22 23:10:10 2024 daemon.err hostapd: Line 81: unknown configuration item 'wnm_sleep_mode_no_keys'
Fri Mar 22 23:10:10 2024 daemon.err hostapd: Line 82: unknown configuration item 'bss_transition'
Fri Mar 22 23:10:10 2024 daemon.err hostapd: 3 errors found in configuration file ''
Fri Mar 22 23:10:10 2024 daemon.err hostapd: Failed to set up interface with data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=DE ieee80211d=1 hw_mode=g supported_rates=60 90 120 180 240 360 480 540 basic_rates=60 120 240 beacon_int=100 chanlist=13 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40-][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ax=1 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=8 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_mu_edca_ac_vi_ecwmin=5 he_mu_edca_ac_vi_ecwmax=7 he
Fri Mar 22 23:10:10 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy0 ifname=phy0-ap0
Fri Mar 22 23:10:11 2024 daemon.notice hostapd: Set new config for phy phy1: /var/run/hostapd-phy1.conf
Fri Mar 22 23:10:11 2024 daemon.notice hostapd: Restart interface for phy phy1
Fri Mar 22 23:10:11 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=DE ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=36 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-2][MAX-MPDU-7991][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=1 he_oper_centr_freq_seg0_idx=42 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=8 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 86: unknown configuration item 'wnm_sleep_mode'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 87: unknown configuration item 'wnm_sleep_mode_no_keys'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 88: unknown configuration item 'bss_transition'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 138: unknown configuration item 'wnm_sleep_mode'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 139: unknown configuration item 'wnm_sleep_mode_no_keys'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 140: unknown configuration item 'bss_transition'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 190: unknown configuration item 'wnm_sleep_mode'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 191: unknown configuration item 'wnm_sleep_mode_no_keys'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Line 192: unknown configuration item 'bss_transition'
Fri Mar 22 23:10:11 2024 daemon.err hostapd: 9 errors found in configuration file ''
Fri Mar 22 23:10:11 2024 daemon.err hostapd: Failed to set up interface with data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=DE ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=36 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-2][BF-ANTENNA-2][MAX-MPDU-7991][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=1 he_oper_centr_freq_seg0_idx=42 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=8 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0
Fri Mar 22 23:10:11 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy1 ifname=phy1-ap0
There is not official release statement for 23.05.3 yet.
Try to find if such bug is documented in 23.05 snapshot or main. If so it is likely to be solved in a near future.