I hoped to be able to use luci attended sysupgrade, but it says No upgrade available: does it only chack against the latest available version?
I re-skimmed the release notes and notice that it can't be upgraded directly, but using 22.02.x as intermediate seems to be possible?
If I have to upgrade manually: where can I obtain a 22.03.x intermediate image?
Is it possible to (manually) taylor the upgrade to 22.03.x in order to keep my installed components and backed up settings (35 files)?
(I hope then to be able to use attended sysupgrade from 22.03.x).
And last: is it possible to downgrade?
Regards
Save config backup to downgrade.
auc will not do 22->23 well best to start with default sysupgrades.
Thanks - so I'll sysupgrade to 22.03.6 (I found it), and continue immediately to 23.05.5.
I'll not apply my backup or install modules to 22.03.6, but wait to 23.05.5.
Does
Keep original config backup, if sysupgrade shows red on image format you need to do complete reset and retype old backup.
I did as suggested and made two sysupgrades without problems.
I then had a problem with my old Huawei E3372h-153 USB 4G dongle, because it wasn't enabled - and my only internet connection...
After reading my notes from the 21.02.1 installation three years ago, and some tweaking using another router, I managed to install the correct modules and make it connect to the internet.
Thanks again.
Yes, i did not say very clearly that after generic sysupgrades you need to add back luci-proto luci-app and similar frontends.
- and I was cheering to early: I only managed to get internet connection from the router itself, but not from any clients...
The firewall has changed to firewall4 and doesn't understand my IP-ranges (format: ip1-ip2) which I used to control internet access for clusters of predefined clients.
I removed firewall4, renamed /etc/config/firewall, and reinstalled firewall4, and now it seems to work.
Trying to figure out how to specify an IP-range (like the old one) using firewall4...
Reading documentation and posts hasn't helped so far.
You can still have firewall3 (package name firewall) , it is instrumented in luci.
In principle you can report even years overdue that config entered in fw3 does not reflect correctly in fw4.
I know from the release notes that a new firewall is in place, I'm just making a note of the non-trivial differences in the configurations (for my use).
I'll try to stick to firewall4 for now.
In principle you can use nftable sets to group address ranges then use in rules. I dont think ranges were ever accepted via luci as is per rule.
No, but installing iptables-mod-iprange enabled IP ranges to be specified in luci via the extra field, in my case (taken from firewall3 /etc/config/firewall):
extra '-m iprange --src-range 10.0.0.200-10.0.0.219'
I can't confirm the name on the field in luci+firewall3, as I'm on a newer vesion now - but the IP range was input in the luci GUI, which I very much prefer over text editing config-files and maybe not being able to see it in the GUI afterwards.
You can enter ranges (easier editing config file as input box is at the end of expanded known addresses)
Rule doc:
https://wiki.nftables.org/wiki-nftables/index.php/Supported_features_compared_to_xtables#iprange
You're right, thanks.
If there is anything else around custom rules just post it here, we can figure it out.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.