Hello, I also use PPPoE and I have no problems with DHCP-PD. I have a Redmi ax6000 and it's on version 23.05rc2. Whenever I update I make a backup of the settings and IPv6 has been working very well here
1 Like
after 10 days, still no issues with my 3 TP-link Deco M4R devices.
1 Like
It appears software flow offloading on mevbu was broken with 5.15 kernel:
2 Likes
RC2 installed and running well on MikroTix hEX (RB750Gr3). WAN throughput slightly UP with latency slightly down (both good). 3 VLANs, adblock and UPnP all ok
Broken:- luci-app-ddns, - Menu item listed but displays error on opening
Broken:- luci-app-https-dns-proxy,, app works when configured from cli but menu item doesnt appear
Looking forward to general release
I see that the Aruba AP115 is included in the list of newly supported devices, is there any more info on this regards with installation method? is it similar to another model?
Thanks
maybe the wiki knows more about it.
Thanks
Just what I was after
Unfortunately it wasn't plain sailing to put rc2 on a Linksys MR8300 today, despite setting the kernsize variable to 500000 before starting. I had 22.03.4 on the second partition and flashed 23.05.0-rc2 (factory-image) from there.
After setting up a serial connection, I saw that the router reported
## Booting kernel from FIT Image at 84000000 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!
Of course, with run bootpart2 I could still boot from my old OpenWrt.
In the end, I loaded 23.05.0-rc2 with tftp (you have to set a PC as a tftp-server, the address the router is looking for can be seen by issuing printenv from an U-Boot prompt), see the instructions here, booted that image, then proceeded to download an image on the router (i.e. in OpenWrt) and flashed it with sysupgrade.
Then I had a functional router again 
Despite having the serial dongle + wires around the house for a long time, it was the first time I used it, everything seems OK.
1 Like
Thanks for the feedback @Erik_Ode I'll wait for a final release before flashing my MR8300
Just FYI ... I've been running a clean install rc1 (ramips/mt7621) 'auc' upgraded to rc2, then installed luci-app-ddns: working without any issues to report.
Weird, I've been running RC1 and now RC2 (via sysupgrade) on the MR8300 without problems after setting the kernsize.
Glad to hear it - I do not rule out that I did something wrong at some point, but I double-checked before I started and the kernsize was definitely fine. Fortunately I could get the MR8300 to work again. Just felt it would be good to document some steps in case anybody else needs them at some point.
It's been running without fault since yesterday so it's definitely been worth the effort. I like the look over the Netgear WAX206, which has been running OK also. I am being a little cautious with my verdict on the WAX206 because I did encounter some flaky connections when streaming audio/video (on wired connections), but so far I haven't found the root cause of that (could also be congestion at my provider, for example). On the MR8300 no issues at all so far.
1 Like
Happy to report that tx_amsdu enabled works well on OpenWrt 23.05.0-rc2 r23228 and WRT1900ACSv2
1 Like
Hi,
New elements added in the issue
A few issues that I would like to confirm / refute in a wider audience:
[23.05-rc2] ipq806x: wireguard performance is much worse compared to 22.03.5
[23.05-rc2, snapshot] 802.11s (mesh) use only 20MHz BW (2.4 GHz)
[23.05-rc2, snapshot] 802.11s (mesh): Could not select hw_mode and channel. (-3)
2 Likes
ipq806x may be in it’s maturity stage but I don’t see a reason to think of discontinuing support for this SoC family and the devices at this time.
ipq806x devices like Netgear R7800 with 128 MiB flash, 512 MiB memory, AC wave 2 wifi and ARMv7 dual core SoC running at 1.7 GHz should not be seen generally as outdated in 2023.
9 Likes
interesting due to lack of issues and errors is there will be rc3 or initial release? due to only 2rc's it will be most stable release since 19.xx! GREAT JOB OpenWrt developers and community!
I don't know if this is relasted to 23.05.RC2
but after 18d 3h 17m 25s
I get this.
[ 72.964751] br-lan: port 3(phy0-ap0) entered disabled state
[ 74.289646] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[ 74.296987] br-lan: port 3(phy0-ap0) entered blocking state
[ 74.302763] br-lan: port 3(phy0-ap0) entered forwarding state
[235595.858123] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[244968.017851] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[244968.027405] ath10k_pci 0000:00:00.0: Invalid peer id 151 peer stats buffer
[356302.254496] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[585121.127678] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[745191.602809] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[746769.884357] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[746770.905491] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[747541.060810] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[747542.087503] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[747543.111611] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[747544.131389] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[749892.696141] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[749893.686718] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[749894.709647] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[749895.816902] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[750648.459529] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[750656.744176] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[750656.765692] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[750658.262882] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[752722.002577] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[759784.054117] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[762690.976829] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[763733.707403] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[763736.959648] ath10k_pci 0000:00:00.0: Spurious quick kickout for STA 3c:e9:f7:f4:32:56
[771422.882020] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[790538.881442] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[848787.439680] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[854942.959507] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[854942.968778] ath10k_pci 0000:00:00.0: Invalid peer id 475 peer stats buffer
[1138912.630979] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[1188131.749511] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[1350190.304627] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[1364253.104238] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[1390193.743476] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[1446627.581797] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
and some of my devices(iphone, LG-tv) are kicked out of the network.
My laptop(3c:e9:f7:f4:32:56) shown in the log still was able to connect to the internet. but it can also be that my laptop was able to connect to another accesspoint as it was nicely kicket out while my other devices didn't I don't know but suddenly dropping connection is an issue for me.
On RC1, this issue happened every 4 days, so it's progress at least.
There are still 23.05-SNAPSHOT builds getting built, but you'd have to look to see if there have been code changes -- unless they only make new builds when there have been code changes. I don't know the answer to that:
https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/
Some people on 23.05 RC2 have reported their 5GHz devices getting kicked off after some period of time (which is a bug going back numerous releases, though), so it's not beyond the realm of possibility that something similar is going on with yours (you didn't say which frequency you happened to be using on the devices that got kicked off, or which router you're using). See thread starting here:
4 Likes