Following the chain of related issues, I landed at Disappearing DHCP Offers & bridge ageing_time and https://github.com/freifunk-berlin/bbb-configs/pull/481/files
Setting ageing_time to a small value on the bridge config might help work around the issue?
(My experiments so far tonight have been inconclusive but promising.)
Actually, the firmware selector's package customization started working for me (Ras Pi 4B) the day after I posted that, so about seven days ago. I've since moved to RC1. If it's still not working for you, that does sound unusual. Assuming you're on a supported device (see release notes), you may want to check again. If it still happens, maybe let the developers know.
R7800 craches
Second OOPS in a view days, ramoops:
Unable to handle kernel NULL pointer dereference at virtual address 0000000c
[33763.436846] pgd = 5a6825a0
[33763.445085] [0000000c] *pgd=00000000
[33763.447604] Internal error: Oops: 17 [#18] SMP ARM
[33763.451338] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet ath10k_pci ath10k_core ath wireguard pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211 libchacha20poly1305 curve25519_neon cfg80211 slhc poly1305_arm nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcurve25519_generic libcrc32c crc_ccitt compat chacha_neon ledtrig_usbport ip6_gre ip_gre gre ip6_udp_tunnel udp_tunnel ip6_tunnel tunnel6 ip_tunnel sha512_arm seqiv kpp cmac uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom ohci_platform ohci_hcd phy_qcom_ipq806x_usb ahci fsl_mph_dr_of ehci_platform ehci_fsl sd_mod ahci_platform libahci_platform libahci libata scsi_mod
[33763.452003] scsi_common ehci_hcd ramoops reed_solomon pstore gpio_button_hotplug ext4 mbcache jbd2 crc32c_generic
[33763.543014] CPU: 0 PID: 13270 Comm: smbd[10.20.0.14 Not tainted 5.15.114 #0
I confirm, just tested on Linksys EA8300 radio 0 not working at all:
2023-06-20T15:15:15+02:00 OpenWRT netifd: radio0 (18530): Command failed: ubus call hostapd config_add {"iface":"phy0-ap0", "config":"/var/run/hostapd-phy0.conf"} (Invalid argument)
that is with the default configuration for wireless.
Radio 1 and 2 appear to be OK, however I did not have time to run more tests as I had to revert back to 22.03 quickly to restore my WiFi network.
23.05 working fine on EA8500 and WRT 32x so far.
1 Like
Installed on Sitecom WLR-8100 and WLR-7100 devices using SYSUPGRADE and kept the settings.
All in working order.
The WLR-7100 serves as wired managed switch, wireless (both radios) was off before upgrade and stayed off, also as such indicated in luci.
SQM for luci also works.
No issues so far with the Sitecom WLR-8100 and WLR-7100.
Thanks for keeping support for selected Sitecom devices in good working order!
So VLAN filtering still not fully fixed with 23.05.0-rc1 for mvebu?
No, but looks like the commit made it in so should be good in rc2. Kernel 6.1 should better fix it but that's a ways off. You can read about it on the github links, there are a few more related to the bugs themselves if you search around.
1 Like
Ok thanks. I was about to give 23.05.0-rc1 a try as I'm still using 19.07.10 with my WRT3200ACM but I need a proper function VLAN filtering so I guess I'll have to wait... 
For whatever reason, it appears Software Offloading is causing all browsing activity to cease. I have had to now turn it off. The router (WRT32x) still initiates connections over the internet and DNS queries succeed but any browsing activity is stopped when this mode is enabled on the firewall. Something has changed to cause this. Unless i am mistaken, believe it comes enabled by default?
Running an older 22.03 on another similar device and both software and hardware offloading is enabled. I do recall many previous builds also allowed this to work (IIRC hardware offloading was missing?) and indeed there were benefits so it appears something has changed of late.
If anyone could confirm, i'd be grateful.
Rgds
Pops
Hello friends 
since upgrading to 23.05-rc1 on Mikrotik hap ac2, my cron job do not enable wifi.
I tried commands with uci:
/sbin/uci set wireless.radio0.disabled="0"
/sbin/uci commit
/sbin/wifi reload
radio seems to be enabled, but network isnt emitted.
uci show wireless
wireless.radio0.disabled='0'
at systemlog there is nothing related, only two rows:
Thu Jun 22 08:00:00 2023 cron.err crond[8635]: USER root pid 9170 cmd /bin/sh /wifi2gup.sh Thu Jun 22 08:00:01 2023 daemon.notice netifd: Wireless device 'radio0' is now up
wifi is only working when I enable / disable it via web ui.
Is this the complete output of the command uci show wireless?
If so, the entire config is missing. If not, you may wish to create a topic including all relevant information.
Firewall Software Offload? That is an experimental feature that is not enabled by default and is broken with MVEBU devices with the latest builds.
2 Likes
Thank you, been tracking MVEBU development for a while and hadn't noticed this. Quite a shame that it remains broken, it did yield benefits when it ran well on the older kernels with symmetrical gigabit connections.
maybe a solution is skipping the 5.15 kernel and using the 6.1 kernel on openwrt 23.05
The 23.05 branch will always use the 5.15 kernel. 6.1 won't be until the next release branch after 23.05. That's not expected to come until next year at the earliest.
The OpenWrt team does about one major release per year (2020 being an exception), based on specific LTS kernel series.
- LEDE 17.01: 4.4 kernels
- OpenWrt 18.06: either 4.9 or 4.14 kernels, depending on hardware target
- OpenWrt 19.07: 4.14 kernels
- OpenWrt 21.02: 5.4 kernels
- OpenWrt 22.03: 5.10 kernels
- OpenWrt 23.05: 5.15 kernels
4 Likes
if so will have to wait for the release in the next year
In the meantime, you may want to test a snapshot release. Some targets have already switched to 6.1. More will come.
2 Likes
Correct, but to be clear, people should not install snapshots of OpenWrt main (formerly known as "master") without understanding what they're getting into. For example, those builds are completely untested, do not include LuCI by default, and require very frequent updating to keep up with package dependencies such as kernel modules.
More info: https://openwrt.org/releases/snapshot
PS- There are also snapshots of the release branches (e.g. 22.03-snapshot, 23.05 snapshot), and those do include LuCI by default. However, none of the current branches will have a 6.1 kernel. That won't happen until the next major OpenWrt series after 23.05 branches off from main next year (or whenever it'll end up being).
1 Like
I have tested the snapshot on Linksys E8450. Result: no WiFi. Reverted to 22.03.5. Won't test 23.05.0-rc1 because of the broken firmware selector.
I using snapshot on my ax6, kernel 6.1.34
I don't see any big issue in my home.
Wifi+FT
Mwan3
Adblock
DoH
Zerotier
I always build all package (Inc Luci, root password, local ip add) using https://firmware-selector.openwrt.org/