OpenWrt 23.05.0-rc3 - Third Release Candidate

I don't think you can select any channels except 36, 52, 100, 116, 132, 149 and 165 (some might not be available in your country). This is by-design to not overlap with other networks.

2 Likes

36, 40 and 44 works fine with 80mhz but not 48 on wrt32x

You may have done something wrong, my WRT32X is flawless with bufferbloat, the results I posted above, WRT3200ACM is the same hardware. Under SQM QoS in Luci did you you forget to set the switchport to wan/wan6?

2 Likes

Hello phinn, thanks for replying, I havent changed any settings, SQM I havent installed anymore in RC3 build, only qosify... I confess, before, I had SQM installed, but was deactivated, not enabled, so I thought, maybe its better, to dont install SQM, if you dont have it enabled anyways.... (thinking to myself) ...should I pull new image with SQM and qosify and the other stuff... and then retry.. ? you opinion, is always much appreciated.. Thanks

ill come back later, and re flash with anew build including SQM like I had it before...will see... and let you know phinn

You could try jumping back and forth between rc2 and rc3 pretty quickly with auc. It will keep your config as-is and allow you to test both in pretty quick succession.

$ opkg update ; opkg install auc # in case you don't already have it
$ auc -y -b 23.05 -B 23.05.0-rc2
$ auc -y -b 23.05 -B 23.05.0-rc3

This installs and reboots automatically with the specified version.

2 Likes

Hi efahl, Ill try, yes using auc.... will test, as on the other partition I have still RC2

1 Like

It didnt got better, pulled new RC3, played back my backupfile from RC2 ...rebootet twice and result is ->

I slowly, believe, its maybe a Mullvad Problem (my VPN Provider) or ISP Vodafone Kabel Deutschland... I mean, 14% Packet loss, somehow, makes me think, someone touched the connection box in cellar, you will laugh, it already happened, screws been loosening, or corrodet, or damaged or shielding damaged or touched other connections... will wait to sunday, to see if it gets better, if not, Ill call ISP ( I hate Vodafone, full house of idiots working there) and initiate they come here and make their measurements and open connection box in cellar and see whats going on, here at home, nothing is damaged, did cable test, the problem must be outside..in my believing... why should suddenly a setup, that worked perfectly many many month superbly well... be invalid or broken...I cant believe that...

Ha ha, that's nothing. I worked in an office once with 6x bonded T1s, which ran out to a service box about 30 meters from the Pacific Ocean. The box was a open air steel thing, with rust holes and moss growing on it. The phone company had to come out and replace the boards every six months because of the salt water turned the traces into green slime. I couldn't believe they didn't just replace the box with something air and water tight, but "it's not in the budget"...

3 Likes

rc3 seems to be running fine on a Xunlong Orange Pi R1 Plus LTS. Thnx

I can't speak to Qosify don't know anything about it. I've used SQM for years on our target (wrt32x / wrt3200acm) and it works perfect, +0ms dl/ul zero bufferbloat, A+ ratings.

Here is my results I linked above: [https://www.waveform.com/tools/bufferbloat?test-id=7f54025b-a6aa-4191-aa19-18d0ef64b58a]

Just install luci-app-sqm (it'll automatically add the deps), in Luci: enable SQM, set interface to WAN, set dl/ul limit to 95% of your speed tests, leave cake as default, set link layer adaptation overhead (e.g. Ethernet w/Overhead 22 for cable) and it's zero bufferbloat up to about 500Mbits or so limit, it'll start getting CPU limited on CPU0, still have headroom left on CPU1.

2 Likes

just a test with ca cake and script dscp router RT3200

my bufferbloat is insane

1 Like

great advice. adding a little biut of ethernet overhead (not the default) tremendously stabilised by bufferbloat much more thran dropping max transfer rate excessively.

Problem is fixed, I called ISP, then, they said me they give it to Level 2 support, and then, after 20 mins, nothing worked anymore.. and now, suddenly after 4 hours, my router reconected to Mullvad and DNS working again, they did something, Bufferbloat is again below 2 ms or better on up and download, and also package loss is fixed... as I see, dropped frames in qosify stats, is very small...not like before...10000 dropped frames I sometimes saw.... Im sorry, I ve been posting about it, but i was so unsure... what could have been the reason..at the end, my instinct, was correct, that problem wasnt RC3 ...but ISP

3 Likes

only custom build with patches from pull #13200
I've did test on my spare FB7412 and errors got away.
Seems not enough lantiq users now where you can get VDSL on FB7520/7530

Update on TP-Link EAP615-Wall (access point) and Raspberry Pi 4 (router) went ok.
With adblock-lean + SQM I now have Bufferfloat A+
(while in 22.03.5 with adblock + SQM I had Bufferfloat A)

I've updated a Belkin RT1800, a ZTE MF286D and a Netgear WAX202, all good so far.

Thanks so much for your work guys!

1 Like

I wanted to test this release but I just recognized that some of my devices (Fritzbox 7412 and Fritzbox 7362 SL) are no longer supported or at least no images are available. Is there any information available why these devices have been removed. In general both have enough flash/memory.

Mentioned in the release notes under Known Issues (lantiq), but not the first post.

on " TP-Link Deco M4R v2" I still have issue dropping all 5Ghz connections at once(same issue as in RC1 and 2),
I now replaced non-ct driver by ct driver, hope this makes a difference, but in my earlier XP I don't think it will.

just installed rc3 on my Linksys WRT3200ACM.

Installation was a headache when I tried to keep settings. It installed OK but although I could connect to the internet via ethernet the wifi interface continued to be not-associated and the usual tweaks did not restore it..

OPKG update failed too with error 6, which is usually an internet connection error

So I did the job properly and did a clean install. It worked flawlessly this time and so far is working well. It even seemed to have cured an error which has just appeared where my Draytek wireless AP kept dropping the connections, although I need to monitor this.
As always, many thanks to the devs for all their hard work

UPDATE - the issues with dropped connections from my Draytek have not been fixed. But they predate RC3 and so are not to do with that

2 Likes