Quick question, does the current 22.03.0stable release include your patch(s) as well?
I tried reading the posted changelog but the bleepin' commit diff? is not in any alphabetical or numerical order. Unless there is some trick to it that I'm missing ...
After a week of testing I've just taken the plunge and migrated my entire home/office network to this, including two separate telecommute/VPN users on gigabit fiber and 4 separate VLANs.
It's working spectacularly; total bandwidth and responsiveness are impressive; basically ~930mbps WAN:LAN(s), all you can expect with PPPoE -- and pretty nearly that bidirectionally -- and there's almost never any measurable CPU load.
The only negative result of moving away from a quad-NIC x86_64 solution is that now I only get a total 1Gb/s (aka "500/500" as noted above) bandwidth when routing internally between VLANs. But that's never going to be a problem in real life: my network design is such that it's very unusual to need to move large files between VLANs: everything with a disk drive sits on a single VLAN, the rest are either simple devices (e.g. IoT) and lightweight streamers on the one hand, or fully-isolated paths for VPN tunnels terminated on other devices on the other. The MT7621 in this scenario is all network appliance and no application.
Even DNS is handled by a separate device; I've connected up an old $5 Pi Zero to the router's USB2 port as an ethernet gadget and it's running AdGuard Home; the MT7621/OpenWRT/dnsmasq only handles local hostname resolution.
Admittedly one factor that makes this easy is I don't really need traffic shaping. If I ever do, I may still keep this device in an edge role to handle PPPoE/NAT, and put my x86_64 device back into service as a core router and shaper. Until then, there's a lot to be said for application-specific silicon over brute-force CPU.
I don't think we can preserve the section ids, flow_offloading and flow_offloading_hw this way, which would break compatibility with old uci configurations and break more things. I've made a small fix with a friend which hides the other option when one is selected.
My change won't be accepted because it contradicts with the implementation on firewall3 and firewall4. The current way on LuCI cannot be changed because of this. Check @jow's reply on the pull request.
I'd really like to try your build on my Xiaomi Redmi 2100 but the page linked in the topic seems to have been cleared off of those images and according to my understanding only recent snapshot images are baked in with the patch.
Is it possible to grab a non snapshot image from somewhere?
Doesn't have to be the latest official version...
I kinda know my way around customising and compiling my own images but integrating patches is beyond my current skillset... Not for the lack of tryng though...
I just couldn't find a resource that describes the process using terminology that I could wrap my head around...
Cheers.
Not sure how the trunk/branch/release cycle happens here. If recent snapshot images have your patches, does that also mean that the just-released 22.03.1 and 21.02.4 releases also have them, or that some future official stable release will have them?
The comment you replied to already explains this but it'd be great if you could also confirm the same behaviour I was getting on my EdgeRouter X SFP. I don't have access to the device anymore and need someone else to do a few tests on it along with this.