OpenWrt 23.05.0-rc2 - Second Release Candidate

jbrossard · July 31, 2023, 7:20pm

Thanks. I'll wait until RC3.

phinn · July 31, 2023, 9:49pm

Luci overview looks unchanged in rc2. I do hope someone would tweak the dark theme so that the Wireless radios aren't white bg/ grey text anymore.

edit: @grifo ah thanks just updated the package and there is port status. I know it's advised against but simply updating it worked fine for me. That's great to see, could use a tweak the spacing is a bit far apart.

MooMan · August 1, 2023, 12:50am

HI & Cheers, for me, on my WRT3200 ACM, it worked directly after last update, and I updated some weeks ago (when RC2 came out) from 22.03.2 directly to 22.05.0 RC2.. and then, just did the newly appearing updates from Luci Software Menu, I refer to the new Port Status info that shows up on Status, Overview Menu

psherman · August 3, 2023, 5:48pm

6 posts were merged into an existing topic: Syn flood protection for FORWARD?

Seele-Vollerei32 · August 8, 2023, 10:00am

I flashed the latest version of 23.05 (self-build) and the device cannot boot anymore(and also the 23.05-rc2), but it can boot with initramfs(both of my build and firmware-selector), I suppose there is something went wrong with mtd1(mibib). So what can I do to debrick the router?

Seele-Vollerei32 · August 8, 2023, 10:05am

additionally, I found a mibib file from my uboot provider(I'm not using the official uboot), but it can't flash and returns Could not open mtd device: /dev/mtd1

hecatae · August 8, 2023, 10:37am

Absolutely no idea what device you are using, I recommend opening your own thread detailing what device you have and how you installed rc2.

lleachii · August 9, 2023, 12:25pm

That information is in Post No. 1.

donh · August 9, 2023, 4:41pm

Why not use https://firmware-selector.openwrt.org/ and see if they have what you need?

hecatae · August 10, 2023, 10:14am

anyone using AUC to keep the rc2 release up to date?

ghoffman · August 10, 2023, 10:18am

yes; it works.

mikko70 · August 12, 2023, 6:22am

Hi
RC releases are quite old now, what are main things, what block final version release?

openwrtforever · August 12, 2023, 6:47am

I was thinking the same, I thought this project just died.

Llethur · August 12, 2023, 7:33am

If you look at the cadence of releases of previous years from release candidates to stable releases, the current gap shouldn't be concerning.

antoinel · August 12, 2023, 7:34am

Pretty sure it's the annual holidays and I believe there are a bunch of open issues with the 23.x. So I don't think the final version is coming soon. Looking at the issues trackers, I noted the following:

https://github.com/openwrt/openwrt/issues/10224 (predate 23.x, seems major)
https://github.com/openwrt/openwrt/issues/13050
https://github.com/openwrt/openwrt/issues/13156
https://github.com/openwrt/openwrt/issues/12882
https://github.com/openwrt/openwrt/issues/12874
https://github.com/openwrt/openwrt/issues/13045

4zims · August 12, 2023, 8:15am

also this one

github.com/openwrt/openwrt

Disabling wifi in LuCI fails in most cases

opened 07:07AM - 08 Jan 23 UTC

Djfe

bug

### Describe the bug I have issues disabling my WiFi radio using LuCI: ``` …Sun Jan 8 03:02:52 2023 kern.info kernel: [ 397.354591] device phy0-ap0 left promiscuous mode Sun Jan 8 03:02:52 2023 kern.info kernel: [ 397.359704] br-lan: port 4(phy0-ap0) entered disabled state Sun Jan 8 03:02:53 2023 daemon.notice netifd: radio0 (4666): WARNING: Variable 'data' does not exist or is not an array/object Sun Jan 8 03:02:53 2023 daemon.notice netifd: radio0 (4666): Bug: PHY is undefined for device 'radio0' Sun Jan 8 03:02:53 2023 daemon.notice netifd: Wireless device 'radio0' is now down ``` This appears to affect other devices as well. Maybe it's limited to the radios of the MT76 driver though. I'm planning on doing some bisection on an older device (D-Link DIR-860L) to find the version or maybe even the commit that introduced this bug. In-case it even is a regression. ### OpenWrt version r21727-3c31f6b521 ### OpenWrt target/subtarget ramips/mt7621 ### Device ASUS RT-AX53U ### Image kind Self-built image ### Steps to reproduce Boot Use LuCI to config WiFi and then enable 2.4GHz radio. Disable said radio. ### Actual behaviour Radio stays online, I can still see the SSID but connecting to the WiFi fails. WiFi LED also keeps blinking (indicating that WiFi is in fact still turned on). ### Expected behaviour The radio should go offline instead of broadcasting the SSID. ### Additional info This bug specifically doesn't affect `wifi down`, that command works flawlessly everytime. If I boot with WiFi already enabled, then disabling WiFi using LuCI works for the first time. The LEDs turn off etc. Turning it on and then off again the second and all further attempts fail. You can see the error log in the bug description above. **A successful attempt looks like this:** ``` Wed Jan 4 03:21:20 2023 kern.info kernel: [12797.346347] device phy0-ap0 left promiscuous mode Wed Jan 4 03:21:20 2023 kern.info kernel: [12797.351418] br-lan: port 4(phy0-ap0) entered disabled state Wed Jan 4 03:21:20 2023 daemon.notice hostapd: Remove interface 'phy0-ap0' Wed Jan 4 03:21:20 2023 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED Wed Jan 4 03:21:20 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED Wed Jan 4 03:21:20 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING Wed Jan 4 03:21:20 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied Wed Jan 4 03:21:20 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0 Wed Jan 4 03:21:20 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap0 from bridge br-lan: Invalid argument Wed Jan 4 03:21:20 2023 daemon.notice netifd: Wireless device 'radio0' is now down ``` ~~I'm wondering whether the following two lines from a successful attempt play a role in this. The errors are obviously not intentional.~~ (EDIT: I was able to rule this out by testing on a DIR-860L (see post [3](https://github.com/openwrt/openwrt/issues/11725#issuecomment-1379912719)) ``` Wed Jan 4 03:21:20 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied Wed Jan 4 03:21:20 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap0 from bridge br-lan: Invalid argument ``` **Related Issues:** https://github.com/openwrt/openwrt/issues/11068#issuecomment-1371156201 https://github.com/openwrt/openwrt/pull/11220#issuecomment-1336263591 https://github.com/openwrt/mt76/issues/601#issue-1016641812 https://github.com/openwrt/openwrt/issues/7485 (peculiar: in my case LEDs always light up on radio activity unlike for the reporter, for me it's just that the led/radio stays alive when it should be offline) **Related Code** (that introduced the error message and might tell us where to look)**:** https://github.com/openwrt/openwrt/pull/4314 https://github.com/openwrt/openwrt/commit/6603748e0ca697f484adfc16a0d49d35ed36954d (maybe?) Feels like the 'data' variable wherever it is, wasn't initialized/set correctly and therefore the default 'radio0' is used which obviously doesn't exist. Though I have no clue which code files to look through 😅 What does LuCI do differently compared to `wifi down`? ### Diffconfig ```text tmp/.config-package.in:56656:error: recursive dependency detected! tmp/.config-package.in:56656: symbol PACKAGE_luci-app-pbr depends on PACKAGE_luci-app-pbr For a resolution refer to Documentation/kbuild/kconfig-language.rst subsection "Kconfig recursive dependency limitations" tmp/.config-package.in:56656:error: recursive dependency detected! tmp/.config-package.in:56656: symbol PACKAGE_luci-app-pbr depends on PACKAGE_luci-app-pbr For a resolution refer to Documentation/kbuild/kconfig-language.rst subsection "Kconfig recursive dependency limitations" CONFIG_TARGET_ramips=y CONFIG_TARGET_ramips_mt7621=y CONFIG_TARGET_ramips_mt7621_DEVICE_asus_rt-ax53u=y CONFIG_PACKAGE_attendedsysupgrade-common=y CONFIG_PACKAGE_cgi-io=y CONFIG_PACKAGE_liblucihttp=y CONFIG_PACKAGE_liblucihttp-ucode=y CONFIG_PACKAGE_luci=y CONFIG_PACKAGE_luci-app-attendedsysupgrade=y CONFIG_PACKAGE_luci-app-firewall=y CONFIG_PACKAGE_luci-app-opkg=y CONFIG_PACKAGE_luci-base=y CONFIG_PACKAGE_luci-mod-admin-full=y CONFIG_PACKAGE_luci-mod-network=y CONFIG_PACKAGE_luci-mod-status=y CONFIG_PACKAGE_luci-mod-system=y CONFIG_PACKAGE_luci-proto-ipv6=y CONFIG_PACKAGE_luci-proto-ppp=y CONFIG_PACKAGE_luci-theme-bootstrap=y CONFIG_PACKAGE_rpcd=y CONFIG_PACKAGE_rpcd-mod-file=y CONFIG_PACKAGE_rpcd-mod-iwinfo=y CONFIG_PACKAGE_rpcd-mod-luci=y CONFIG_PACKAGE_rpcd-mod-rpcsys=y CONFIG_PACKAGE_rpcd-mod-rrdns=y CONFIG_PACKAGE_rpcd-mod-ucode=y CONFIG_PACKAGE_ucode-mod-html=y CONFIG_PACKAGE_ucode-mod-math=y CONFIG_PACKAGE_uhttpd=y CONFIG_PACKAGE_uhttpd-mod-ubus=y # CONFIG_TARGET_ROOTFS_INITRAMFS is not set ``` ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

Llethur · August 12, 2023, 9:29am

Some may be on holiday. Progress is still ongoing: OpenWrt Images (S): builder openwrt-23.05_x86/64

mmortal03 · August 12, 2023, 9:41am

There are a number of issues labeled/targeted for the release currently: https://github.com/openwrt/openwrt/issues?q=is%3Aopen+label%3Arelease%2F23.05+sort%3Aupdated-desc

emss · August 12, 2023, 7:01pm

Hi,

DHCPV6-PD is expected to work flawlessly and does not in my setup.
A ticket has been filed without any acknowledgment or inquiries regarding missing information that could help diagnose/fix the issue.
What's the recommended way to get this issue the attention it seems to deserve, please ?

github.com/openwrt/openwrt

[23.05.0-rc2] DHCPV6-PD/PPPoE doesn't work

opened 01:39PM - 10 Jul 23 UTC

emss-github

bug

### Describe the bug Interface startup or restart establishes the link, the pre…fix delegations seems correct, but after a while the router stops forwarding ipv6 packets then from time to time forwards again then stops. The issue seems to be related to odhcp6c as lines like the following pop up in the logs odhcp6c[xxx]: Server returned IA_PD status 'No Binding (NO-BINDING)' network config and ifstatus wan6 result are attached, a pcap of the dhcpv6 exchange is available on request. [ifstatus_wan6.txt](https://github.com/openwrt/openwrt/files/12002444/ifstatus_wan6.txt) [network.txt](https://github.com/openwrt/openwrt/files/12002482/network.txt) ### OpenWrt version r23228-cd17d8df2a ### OpenWrt target/subtarget x86/64 ### Device AZW U59 ### Image kind Official downloaded image ### Steps to reproduce _No response_ ### Actual behaviour _No response_ ### Expected behaviour _No response_ ### Additional info _No response_ ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

BR

nbie · August 14, 2023, 12:03am

WAN speed limited to 100M on WAX206

Settings for wan:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 7
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

Force the WAN speed to 1000M but no connection.
ethtool -s wan speed 1000 duplex full autoneg on

Settings for wan:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 7
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

WAN speed detected correctly on the WAX202

Settings for wan:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes