Thanks for answering I cant test at the moment, but I think there should be some people here eager to try.
EDIT: as currently the firmware is broken, why not apply the path on master? This way it will be easier to test, because people could use the next snapshot build (compiling openwrt is not trivial IMHO)
I just finished building and flashing master with your patch included-- I had to reset then reconfigure the router as the RJ45 ports weren't working (including WAN) when I upgraded with configurations intact.
Here's my build of it (SHA256: 26a34f1db3a84e9122f326813f3fb8cae54b4411483f01230bf34d5427451e8c), though again, while it works for me I'm not exactly sure that I'm doing everything right. I tested Wireguard on this and it does work except for IPv6, though I'm not sure if that's a problem on my end or not.
Can someone make changes to src? Our device have 3 LED instead of 2. They are blue status, orange status and blue+orange, let's say purple. And there are 2 LEDs that we don't have. Let's say in summary: add blue+orange led and delete unused mt76-phy leds
The patch I proposed for testing enables loader for all mt7621 devices and it turns out to break some other routers unaffected by this problem. That's why I want some testing before pushing it to master and now I've abandoned that patch.
booting normally with this build,, , run opkg update, opkg install luci-app-mwan3 but got satisfy_dependency_for error (different kernel).. . add --force-depends and the router can't boot.. . any solutions to install luci-app-mwan3 on non-latest snapshots? edited opkg sources but got same satisfy_x_x error.. .thanks a lot..
@981213@acecilia@ave@juppin thanks all. sorry i'm not able to test the patch because i don't know what should i do ... i need step by step instruction for how to build images with patch included in it.
Ps: My posts were apparently flagged as spam and my main host gets me a "You can't post links to that host" error. I have been using that host to have links not rot like they might on transfer.sh etc and to allow wgeting unlike things like mediafire, so uh... whoever did that, please don't? I don't have an obligation to post builds, I just do that so that others can the most out of their devices without having to build stuff.
Edit: Staff restored the posts and unbanned my host. Thank you! I've updated links in this post to my host too, so that they won't rot.
Get a debian-based linux environment (can be your linux setup, can be a VM, can be an LXC container. I use an debian buster LXC container as my host is arch)
Install required packages
Switch to a non-root account
Clone repo with git
Run ./scripts/feeds update -a and ./scripts/feeds install -a.
Configure it with make menuconfig, this is how 4AGbE looks, pick the packages you want, I recommend setting them to *, not M. M generates them as ipks that you separately need to install (this is what I did to build kmod-ipt-ipset for frosp above). When you're done, hit Save, save as .config.
Start compilation with make.
After a couple hours, the bin file will be in /bin/targets/ramips/mt7621/.
thanks @ave i flashed your image but i don't have access to internet with your build here is serial cosole log:
[ 96.701610] mt7530 mdio-bus:1f wan: Link is Down
[ 99.793555] mt7530 mdio-bus:1f wan: Link is Up - 100Mbps/Full - flow control off
[ 100.797586] mt7530 mdio-bus:1f wan: Link is Down
[ 104.913556] mt7530 mdio-bus:1f wan: Link is Up - 100Mbps/Full - flow control off
[ 105.917584] mt7530 mdio-bus:1f wan: Link is Down
[ 112.081561] mt7530 mdio-bus:1f wan: Link is Up - 100Mbps/Full - flow control off
[ 113.085577] mt7530 mdio-bus:1f wan: Link is Down
[ 117.201581] mt7530 mdio-bus:1f wan: Link is Up - 100Mbps/Full - flow control off
[ 118.205649] mt7530 mdio-bus:1f wan: Link is Down
edit: also have same problem with latest snapshot (Wed Apr 15 16:57:41 2020)
Also, @Zorro, did you upgrade from a version before this commit while keeping your settings? If so, you're likely having the same issue I mentioned here, I personally fixed that by resetting and reconfiguring my device (both from inside luci), but there might be a less nuclear path you might be able to take.
172.28.10.* you cant login to luci.
I can't repro this, I personally use 10.69.0.0/24 without issues.