xize11
8
If I were you I would only neccesary update the opkg package, because that one is compiled within the kernel whereas the update from the adguard may not, sometimes a update can just be a change to the config or init script, but other times it can use a library which is not present due to the kernel limitations, neither do I know if it also compiles libraries or dependencies within this update process, alot could go wrong with this update process, but that is just my opinion.
Tl;tr:
If im correct openwrt has also a adguard package I believe, the closed you can test is trying to compile this with gl-inet sdk on ubuntu, but if that package uses nfttables you even get a more bigger challenge since the latest version of openwrt is going to use nftables rather than iptables which is not in the kernel of flint I believe, or alternatively if you got some programming experience you could checkout a old version or find the source and backport the updates and cherry pick so you can ignore the nftables commit.
But I’d agree this is not suitable for normal users, luckily this limitation will not be forever but it needs time, Im also actively reading the openwrt forums but they still wait for patches by codeaura (qualcomm sdk which is a modified openwrt with closed wifi drivers where flint is based on).
More ax routers from different brands seem to have this limitation of qsdk, but from what I readed is that ipq80xx is being heavily developed on and it has smilliarities with ipq60xx so I’m positive it will soon or late get a updated kernel, also I noticed openwifi, if that can do the same as the closed source drivers by having a quick glimp at their github, the updated kernel could even come earlier, but again I’m not a team member I’m just a opensource enthousiast😁
2 Likes