Switch to OpenWrt 23.05 #1012
Switch to OpenWrt 23.05 #1012
Conversation
- Needs testing, may not be consistent across devices - Have left phy and wl in place where possible
Images cannot be produced sufficiently small. Upstream has marked this as source-only as well. To be dropped in the future unless a miracle happens
- Yes, mvebu is back from the dead
Triggered by u-boot on ramips/mt7620
Several minor cleanups related to the transition to OpenWrt 23.05: - ipq40xx is now a DSA target so sqconfig package no longer required - 23.05 has changed to use wpad-basic-mbedtls so remove WolfSSL packages Also add a couple of gl.Inet, Netgear and Teltonika devices, and remove several device names that no longer appear.
adjust profile_images to match the config
- There is no GUI option for this
… in /usr/lib/bwmon-gargoyle/bwmon-gargoyle.d/ - Created common functions file to remove duplicated functions in each script file (more could be done, this is a starter) - Split Total Bandwidth and Bandwidth Distribution out of bwmon-gargoyle.init into 010-bdist_total.bwmon - Split QoS Bandwidth out of bwmon-gargoyle.init into 020-qos.bwmon - Split Wireguard Bandwidth out of wireguard.firewall into 030-wireguard.bwmon - Split OpenVPN Bandwidth out of openvpn.firewall into 040-openvpn.bwmon - Split TOR Bandwidth out of tor.firewall into 050-tor.bwmon Firewall files now call these individual scripts as well during their up/down calls Before this change, occasionally QoS (and others) would fail to reinitialise their bandwidth monitoring iptables rules. They are now always reinitialised by a restart of bwmon-gargoyle OR a firewall up. Be aware that the QoS Bandwidth iptables rules now have their own chain (instead of sharing with bw_ingress/egress) QoS Bandwidth rules now also apply to IPv6
Unfortunately we end up starting/stopping this twice when changes are made on QoS page, but this does not appear to cause any harm
- Left the modemaccess script in situ as it does work for most users
Fixes UI bugs that we don't want to deal with
- Fixes Chromium based browsers rejecting self signed certificates by downgrading them to version 1 spec
- Also switch from copying the skb to linearising the existing one
32M RAM isn't sufficient to boot Gargoyle without heroic efforts (e.g. using swap on USB) so remove such devices from active support. Affected targets: - ath79/default (6 devices removed) - bcm47xx/default (3 devices removed) - ramips/default (5 devices removed) - ramips/rt305x (5 devices removed)
…base_on_openwrt_2305
|
I will merge this within the week. |
|
Can we move to 24.10? There aren't many changes between 23.05 and 24.10, but at least we'll have the current release. |
|
I am working in the background on switching to nftables. Once this is done I will move to 24.10 so that we don’t have to keep carrying a significant divergence from upstream. nftables is a significant undertaking and the custom kernel modules must be rewritten. The point of merging to master is so I can start a new branch for 24.10 as well. |
|
I was more thinking about the fact that it was 24.10 still with iptables (opkg is standard in 24.10). |
|
I understand. But if I don’t do at least one of those before doing 24.10, I have to do both for 25.xx. |
|
The effort of staying on iptables is frustrating. For every update I need to check if upstream did something nftables only and revert it or rewrite it. There are bugs in fw3 that won’t be solved unless move to fw4. They are written in ucode so back porting fixes is too hard. I am worried that if I don’t do it now it will never happen and eventually it will not be optional. |
Gargoyle 1.15.x is based on OpenWrt 23.05, which is a significant leap forward from 22.03 for 1.14.x.
Configs should generally not be preserved between 1.14 (and earlier) and 1.15.x. Do so at your own risk.
A big thanks to pythonic (Github: aimacintyre) for their assistance and many contributions towards getting this into a position to make it ready for testing.
Notable changes:
Bugs squashed
Things to Note
New Devices
Known Issues
Note: OpenWrt 22.03 moved to nftables from iptables. Gargoyle still uses iptables to support the custom modules it needs, and so there is some package incompatibility with the base openwrt package repository. For normal operation this should not cause a problem. For anyone trying to install extra packages manually, your mileage may vary!