firewall4 now supports include files within existing chains.
See @jow’s comment on Github for the basic syntax:
config include
option type nftables
option path /etc/whatever.nft # avoid /etc/nftables.d/*.nft here since that is still included by default in the old fixed position
# may also be ruleset-prepend (before table) ruleset-append (after table),
# table-prepend (before fist chain in table), table-append (after last chain in table),
# chain-prepend (at top of chain), chain-append (at bottom of chain)
option position table-prepend
# name of chain to prepend/append, only meaningful in conjunction with
# position chain-prepend or chain-append
#option chain 'input_wan'
Reporting an issue too with my tl-wr902ac system. This may be the same issue as huskyhunter reported just above, as I understand both platforms use similar chipsets and radios.
In my setup, the tl-wr902ac has a wifi client connecting over 5GHz to my AP, and a wifi AP on the 2.4 GHz band. The wifi client over 5GHz doesn't work with 22.03.0-rc5, while it was fine with 22.03.0-rc4. The 2.4 GHz wifi AP works fine in either case.
I also updated my main AP (r7800) and my router (wrt1200ac) to rc5, no issues were encountered on these platforms.
The Archer C20 v4 and TL-WR902AC are both 8/64 devices with too little memory to guarantee consistent reliable operation with current OpenWrt releases: https://openwrt.org/tag/64ram
I upgraded my dumb AP - Wrt1900ACS from 21.02.3 to 22.03 RC5 with keeping settings. Both my phones showed Wrong Password and were not able to connect to WIFI. I had to revert back to 21.02.3 and it worked like a charm. I tested 22.03 RC1,3,4,and 5 and the wrong wifi password issue persisted.
No Idea what should be done? Is this a known issue with 22.03? upgrade without keeping setting? Thanks!
After a glorious 240 day uptime on my WRT32X decided to take the plunge to rc5. Did a clean install on the second partition. Added some typical packages, SQM cake running 500/35 Mbits cable speedtest with A+ bufferbloat/ A+ quality results, USB3.0 storage 100 MB/s read-write via Samba, adblock, irqbalance, advanced reboot, etc. nftables/fw4 appears to be seamless, no issues noticed. All good so far, thanks devs.
Fresh install. I patted this RC for 10 hours to learn the newishness of the GUI and liked several item.
Having such a limited CPU it handicapped WireGuard's throughput to 60% of achievable from release I moved from. I've parked my system back to release for now.
Great Job on the RC, I'm sure it's a step up for most users, including me.
No future for OpenWrt 19.07, so I'm going to continue exploring the rc5.
System Board and Opkg Installed
Hostname OpenWrt
Model MikroTik RouterBOARD 951Ui-2nD (hAP)
Architecture Qualcomm Atheros QCA9533 ver 2 rev 0
Target Platform ath79/mikrotik
Firmware Version OpenWrt 22.03.0-rc5 r19523-bfd070e7fa / LuCI openwrt-22.03 branch git-22.167.28394-8a4486a
Kernel Version 5.10.127
I don't do too much with the system, so I normally have about half of the memory free on it. I did not check the free amount under rc5 but I also didn't see anything about being short on memory in the logs.
I have a linksys EA8500 and when installing the ath10k smallbuffers driver it gave me an instability problem, with the ath10k drivers no CT is working normally, I only have qosify and htop for the moment.
Quite possibly this is caused by differing minimum ISA expectations between the different targets, e.g. the RPi foundation didn't license the ARMv8 h/w crypto accleration support for their SOCs, which results in that behaviour if software expects them to be present.
Because with some laptops with windows 10 it disconnects me from the internet, I get the message that says that I am connected but without internet access and I am from version 21.x.x updating as soon as an RC comes out, the problem is since the CT drivers came out, the laptops that moelstan only have cheap network cards that work in 2.4 GHz, in android everything works normal and in 5GHz everything normal, the problem is specific to these two laptops.
I went back to using smallbuffers and everything is working normally, I don't know why the first day it gave me a problem.
I don't know much about the subject, could you tell me what to look for in the event log when something goes wrong? I remember looking the first time it happened to me and since I don't know much about it, I asked for help and they told me that the problem was the ATH10K-CT drivers.
That's why every time I upgrade I install the drivers that are not the candela technologies version or the smallbuffers version.
