All these include a bugfix for the real time clock driver, which did not properly read and set the 12/24 hour mode. The patch has been submitted upstream.
If you are upgrading from OpenWrt 21.02 to 22.03, be aware that 22.03 migrates to the new nftables based firewall4. You may need to take action if you have custom iptables rules (e.g /etc/firewall.user), or applications that interact with iptables rather than nftables (see openwrt/packages: Certain upstream switch to firewall4 aka nftables instead of iptables)
Note: due to a compile breaking change in recent 5.10.12x kernels, the xtables-addons package has been removed from our 21.02 builds.
I am going on vacation for the next couple of weeks, so there wonāt be any updates during that time, except for a major security issues.
SFP information/statistics for LuCI
Also included in the OpenWrt/muvirt 22.03 builds is a new SFP information module for LuCI:
Currently running 22.03 on my Ten64. Working great so far. (Just had to rebuild dropbear to add full ECC support so I can SSH in from my MacBook)
Looking at the āsftp-diagnostics-luciā, it seems it will only ever read board.json, which is probably fine for most boards, however due to the fact I run a customized DPL, my SFPs are eth4 and eth5 and not 8 and 9.
There is currently no ā/etc/config/sfp-diagnosticsā or similar to be able to override the board definitions.
For now I have manually edited board.json to fit my setup, but some overrides might be nice, especially for upstreaming this for devices that might have full PCIe slots so you can add custom NICs etc.
Also, on another note: This might be better moved under the āStatusā tab in LuCi, rather than āNetworkā, following the pattern of where all other things go.
Yes, the interfaces are āhardcodedā by board and I would like to fix this.
In the meantime you can edit /etc/board.d/73_sfp so it refers to the correct interfaces in your case.
The problem in my way at the moment is that there doesnāt seem to be a way to find out (from userspace, like sysfs) what network interface the SFP driver is ultimately controlling. We can figure it out on the Ten64 using restool but I would like a generic solution.
Didnāt realise there were updates: Iāve just sysupgraded and am running OpenWrt 22.03.0-rc5+traverse 585453076 / LuCI openwrt-22.03 branch git-22.167.28394-8a4486a
Initially Iād lost luci, but Iād used the ākeep list of installed packagesā option so I could fix it via opkg install $(cat /etc/backup/installed_packages.txt | awk '{print $1}')
Missing certain things like upnp from the archive but otherwise it seems fine.
The /data mountpoint that Iāve been using on the NVMe drive was missing but the partition was there and untouched.
muvirt will follow, I want to fix a few bugs that have been reported here. As will a new recovery firmware.
I am still tweaking the master branch a bit so itās package selection is slightly out of sync with the others.
(example: the ethtool json patches, SFP LuCI and DPAA2 crypto packages are not there yet)
Do you know if these builds include SSL support in iperf? I noticed that (previous) builds of Traverse OpenWRT included iperf but without SSL support which is available in the iperf-ssl package selection.
SSL support is used for iperf server authentication. Not a huge deal to compile from source but curious on the choice of defaults
Just updated my Ten64 to this, working well so far.
If youāre looking for more possible packages, hereās the ones Iām currently installing that your repo does not have (not sure how important any of those are to other users):
6in4 (most packages needed for this are already in repo, but that one package in base is not)
Stubby: getdns / stubby (DNS-TLS proxy and its library)
Prometheus node exporter: luasocket / uhttpd-mod-lua / prometheus-node-exporter-lua (plus every package beginning with prometheus-node-exporter-lua-, as in, its submodules)
Also, I have to recompile Dropbear to add support for all the public keys (since I use Secretive on macOS which can only generate ecdsa-sha2-nistp keys, you might be in the same boat considering the uVirt version of dropbear includes this support out of the box)
Other packages Iām interested in, but not currently using, because they need kmods which are annoying to compile in my setup:
iPhone tethering (possibly not exhaustive): kmod-usb-net-ipheth usbmuxd libimobiledevice usbutils
muVirt 2022-09-26 (as listed at https://archive.traverse.com.au/) is based on OpenWrt 22.03 exactly, or some few commits later? Is it recommended to install?
Iāve just upgraded from 22.02 and realised that I can no longer create a k3os cluster. Muvirt k3osā master node fails to return the clustertoken plus I cannot connect to the console it seems that even though I can make a dhcp reservation from lan network the eth0 interface gets an 169.254.x.x IP.
btw: BlueKrypto is maintaining k3os upgrades, and it performs well with 5.15 kernel, could be of interest to update k3os downloadurl from k3os-cluster-wizard