When OpenWrt-23.0X is planned to be branched off

I don't see how 23.05 would be any different from previous releases there :stuck_out_tongue_closed_eyes:

3 Likes

compiled from

on ubuntu 22.04
for VMDK x86/64

with bunch of VPN and IPv6 protocols + SNMP + LLDPD

looks good for now

1 Like

Before the actual release (and associated release notes) how would one check to see if their target/subtarget/device has switched to DSA? I'm guessing it's either by searching git commits or by looking at the build configuration files.

I see that ipq806x's config-5.15 file has both CONFIG_NET_DSA=y and CONFIG_SWCONFIG=y, so which is it?

To be clear, yes, I know that this is not a release or even a release candidate, just a series of automated, untested, nightly snapshot builds. I'm familiar with master snapshots and branch snapshots.

swconfig.

2 Likes

well ...
looks like 23.05 want more resources

old: 22.03.5 / new: 23.05

cpu: same / same
disk usage: 25% / 30% of 256MB
ram usage: 60MB / 85MB
same config, same packages, same VM

1 Like

Hi.
Each target has a profiles.json file that lists the defaults packages. For the ipq806x/generic, swconfig is listed.
https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/ipq806x/generic/profiles.json

3 Likes

To be expected unfortunately, bigger kernel again as well. Which is why the deprecation notices for 16 MB flash / 64 MB RAM devices are all the more important.

Just a quick query, I'm guessing that since with previously releases (21 & 22) where's it's been about 5 months between rc1 and the first stable version appearing, the first stable version of 23.05 might be around October/November? Thanks to everyone who works on developing this stuff btw, I've no idea how much work it involves but I'm guessing a lot.

If you're holding out for the actual release, you might be disappointed to find that particular bug your hardware might be suffering from is still in there.

If you're completely risk averse, you should jump on the train with the first RC. Never wait till the actual release.

3 Likes

Or start using the SNAPSHOT builds right now, and help flush out any bugs on the platforms that you care about. Problem reports are always appreciated earlier rather than later!

It is always a good idea - for any developer - to have production platform (running router with stable Openwrt release) and Staging platform to check, test and develop new releases.

By this setup, you can give feedback on errors and bugs which are valuable to know and address at early stages.

4 Likes

Not usually that risk averse, it's just I want to run it on my home router and my wife gets very stern when the WiFi doesn't work.

2 Likes

I ran snapshots a while back but was struggling to even get Luci working. I'm a bit of a noob and with two young kids the hours I spent working on some bugs I had left me a little frazzled. Once sanity returns to my life though I'd love to learn more about this networking stuff and contribute more to the community.

2 Likes

23.05 snapshots will have LuCI built in. If you're on 802.11ax MediaTek hardware, I can tell you master/23.05 is more stable than 22.03.

I understand the reluctance though; so far my wife is more forgiving when I break things :wink:.

2 Likes

I've got a Mochabin, which has a Qualcomm WiFi card. When I tried snapshots with it a few months back Luci wasn't included as standard and didn't work after I installed it, but it's been a while so guess it might have improved. Thinks I'll hold out for the first RC before I take the plunge though. My wife has threatened violence just because I chew too loudly, further loss of WiFi would likely mean weapons.

i can confirm than 23.05 is very cool thanks for all

Hostname	OpenWrt
Model	Linksys E8450 (UBI)
Architecture	ARMv8 Processor rev 4
Target Platform	mediatek/mt7622
Firmware Version	OpenWrt 23.05-SNAPSHOT r23004-7f0db09513 / LuCI openwrt-23.05 branch git-23.118.79121-6fb185f
Kernel Version	5.15.112
Local Time	2023-05-22 19:11:55
Uptime	0h 16m 10s
Load Average	0.00, 0.02, 0.04

i has just a question why many qdisc appair in fq codel like this

root@OpenWrt:~# tc qdisc
qdisc noqueue 0: dev lo root refcnt 2
qdisc mq 0: dev eth0 root
qdisc fq_codel 0: dev eth0 parent :10 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :f limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :e limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :d limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :c limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :b limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :a limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :9 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1518 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64

thanks for advance

Master snapshots (what you tried) don't include LuCI out of the box, but branch snapshots (e.g. 22.03 snapshots or 23.05 snapshots) do include LuCI. But master snapshots are the only type of snapshot mentioned on the downloads page. I only found out about branch snapshots because I stumbled on them once from a random Google search.

To get LuCI on a master snapshot, you have to install it from the command-line using SSH. https://openwrt.org/docs/guide-user/luci/luci.essentials

Master snapshots explained: https://openwrt.org/releases/snapshot
OpenWrt branching explained: https://openwrt.org/about/history#branch_logic

3 Likes

That's why I keep an old router around with the same SSIDs and passwords ready to plug in when something goes wrong. Plug and play, no one the wiser while I reflash and restore.

4 Likes

8 posts were split to a new topic: 23.05 sysupgrade questions