OpenWrt 23.05.2 - Service Release

@phinn thanks, I'm aware of this. Maybe you can clear up the question regarding the table of hardware. Is it just not up to date?

I believe the ToH pulls from the hwdata pages. Lately I've noticed a few of the fields weren't updated automatically for 23.05 or will just show the .0 release. For example my main router mvebu (wrt32x) I updated those manually just to check if ToH was updated with them.

So yea I would stick to firmware selector.

1 Like

In addition to what @phinn said, there's been a lot of work going on related to toh and wiki infrastructure, so the user facing auto-generated and -populated stuff is lagging a bit while that work gets done. aparcar posted on the dev list this morning about some of it:

https://lists.openwrt.org/pipermail/openwrt-adm/2023-December/002447.html

3 Likes

Got the DOCSIS 3.1 CM1200v2 modem (rewewed for $89). Did some tests with my WRT32X (mvebu). I know this isn't a great place to put it, but running 23.05.2:

  • Direct modem to PC: 949 / 37 Mbits, 12ms, +18ms, +38ms, B rating

  • OpenWrt (irqbalance + packet steering): 866 / 37 Mbits, 12ms, +582ms, +41ms, F rating
    (massive bufferbloat introduced with this device. It's only an issue with the upper CPU limit as it didn't do this with 500Mbit internet. Also SFO is also not functional on this target so couldn't be tried).

  • OpenWrt (SQM Cake + irq + ps) : 602 / 31 Mbits, 13ms, +0ms, +0ms, A+ rating
    (99% CPU0, 44% CPU1, found the upper limit for SQM on this target of 600Mbits).

Going to do a lot of tests with the GL-MT6000 when I get it setup, and compile this elsewhere to not hijack the thread further :slight_smile:

5 Likes

Build 23.05.2 on a MX linux (Ubuntu variant) and got the same issue as described here, target is ath79

Remedy is the same as described.

You got an USB WiFi dongle working!!!
Did you get a new one or figure out how to get the one you had earlier?

I have had issues with radio1 wwan1 losing its AP connection but never on the wlan side using radio0.
I use 5Ghz for the lan and 2.4 on the wan; it just tidier when two are blasting out power but, at least, not on the same channel..

Where you able to try out the flint 2 yet? What settings did you end up using?

Can the RP4's built in radio to transmit on 5Ghz and 2.4Ghz at the same time? That is to say, can I set up two access points with radio0 and the same SSID, but two frequencies?

No. For the 5 GHz access point, you can add a USB WiFi card. Alfa Network AWUS036ACM is a good one, but I have been already criticized for this suggestion in the x86 context.

I'm having trouble getting both to work. 5G works fine but if you look at the radio it is not 2 radios but one with 2.4 and 5.

It will let you add the second it but it breaks the install. At least for me. I used a USB dongle as the second radio on 2.4.

:spiral_notepad: It is strange that my pi zero will work as a repeater/travel router; strange because It only has one 2.Ghz radio .

That begs the question:

Why do you think the 5G does not work in the Pi? What version of OpenWrt did you try 5Ghz on what version of the Pi?

I don't have a Pi. However, as you mentioned, the built-in radio is just one radio that can be active on one band at a time, and therefore, you need a USB WiFi adapter to add the second band. Both combinations (2.4 GHs built-in, 5 GHz USB, or vice versa) are known to work. It just makes more sense to assign a premium-quality adapter to 5 GHz.

Regarding the repeater mode, it works as long as both the client and the AP are on the same channel and the WiFi card supports such operation (most of them do). Since OpenWrt 23.05, repeaters work even on 5 GHz DFS channels.

I really should wait until I've had coffee before I post. lol

Yeah, I used an Alfa in the Pi zero w for the wan side; that gives me a strong signal in and the option to use two different channels avoiding interference.

Overall, I am very surprised with the Pi 4 as a router firewall. I have spectrum and they just gave me a modem which passes through the public ip address. and it only uses 0.10% of the cpu at most.

This thread says it should be possible to use both.

I wonder if it is a bonding issue; aka bridge.

What is the premium quality adapter that works? The dongles I've tried receive fine but don't transmit properly. I'm looking for something small. A one antenna dongle.

See https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md and https://github.com/morrownr/USB-WiFi/blob/main/home/Speed_Comparison_Test.md

3 Likes

Thank you for this. I’m sifting through the list for the simplest most compact of the bunch. I’ve got things working perfectly with wan wired and wired lan and wireless lan working perfectly. Trying to connect a dongle that will do 5g and connect to the wan to feed internet to wired and wireless lan.

Is anyone using vnstat (1.x, not 2.x)? I just noticed that none of the wireless interfaces are available to be chosen in its configuration, and if you put them in the config file manually (and restart vntstat) they're ignored. This is not the way it worked in v22 and earlier, so I suspect an incompatibility with v23..Tested in Archer c7v2 and WNDR3800.

I'm hoping not to have to go to vnstat2 (assuming it doesn't have the problem) due to its much larger db size.

Update: I wonder if this relates to ifconfig now using new names for wireless interfaces? What was wlan0 is now phy0-ap0, etc?

Update2: Editing the new interface names into vnstat config, deleting the old corresponding db files, and then restarting vnstat seems to work, though the wireless interfaces are still not listed in Luci's configuration GUI, so it's a bit of a hack.

@rseiler I have a Netgear WNDRMACv2 (same hardware as your WNDR3800) running a custom DD-WRT (modded WNDR3800 firmware to be accepted by the WNDRMACv2). Do you have an idea how to go about switching it to OpenWrt 23.05.2 as easily as possible? I don't have a webrevert to get it back to factory first, so I thought I'd first ask. Thanks!

Wow, that actually is the exact router that I have, but I've used the WNDR3800 FW on it for so long now that that's what I call it now instead.

You have to decide between:

DD-WRT->OpenWRT
DD-WRT->stock->OpenWRT.

I went from stock to OpenWRT. I don't recall how advisable it is to go straight from DD-WRT, but someone either here or there will know. If it's inadvisable, then just do the revert, and from there you're good:

https://downloads.openwrt.org/releases/23.05.2/targets/ath79/generic/openwrt-23.05.2-ath79-generic-netgear_wndr3800-squashfs-factory.img