Daniel Nilsson

To get to parity as before I assume we would need to change `boardinfo.release.description` to `boardinfo.release.description + ' ' + boardinfo.release.revision` at https://github.com/openwrt/luci/blob/c85af3d7618b55c499ce4bf58e3896068bd413ae/modules/luci-mod-status/htdocs/luci-static/resources/view/status/include/10_system.js#L41 I'm a bit unsure where the stable...

>I don't have access to any system at the moment as I'm travelling. So can someone send me the output of /usr/lib/os-release and /etc/openwrt_release, then we can compare and check...

24.10 has now been [branched](https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/openwrt-24.10) without this fix being merged to procd and at least since 19.07 it hasn't had stable branches so backporting doesn't seem trivial in that repo....

We should probably not just hide the Cipher option, a more appropriate solution in my mind is to modify the selectable ciphers to only contain `auto` and `CCMP` when WPA3...

When fixing https://github.com/openwrt/luci/pull/6998 I discovered that I was able to make the menu behave as before by installing `dockerd` on my host. I'm definitely not fluent in Lua but it...

Please don't close you PR:s as soon as you make changes as that makes all the comments get lost, you can just continue pushing to the same branch and your...

> Maybe this package can be forwarded by @systemcrash . > > Look how I messed it up again > >  > > I have to learn again how...

According to [MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea#wrap), `off` is a non-standard solution so we should at least not use that one if possible if we're fixing the wrap behavior anyway.

> @dannil I checked and it works fine in both Chrome and FF: > > https://codepen.io/pcgeek86/pen/ywgWRb Nice, then it should be fine to merge it.

@Ansuel is trying to fix (and upstream) the change with https://github.com/openwrt/telephony/pull/841 but seems they aren't responding.