exactly, but it contradicts what @giuliomagnifico just wrote 
Oh so it has been reopened, some days ago was merged and closed if I saw well! Perhaps I have seen the PR wrong 
Edit: oh now I understand, I was following the PR via mail and I saw only the preview of the penultimate comment “it was merged 
” but it was referring to another commit/pr, ahah sorry my error!
Probably, since I've been keeping a close eye on the PR
1 Like
I think the merge will take some more weeks or even months. 6 approved reviews will take a lot of time ;/
Good that the dev build is working great since months
Thank you Giulio for your kind mail. It's OK to wait the time it takes. I plan to install a VPN router, prior to the main router.
Once again, BIG thanks for all your work and support, which I do appreciate.
Regards
Diego
1 Like
Hello. I'm trying to go back to stock firmware. Sysupgrade -i -F doesn't work. Any advice, pls?
Latest master for Netgear wax 206
Firmware : OpenWrt SNAPSHOT r21967-097e9bf9d8 / LuCI Master git-23.013.73089-9634086
Kernel : 5.15.90
I have updated my wax206 and it runs perfectly - as always
1 Like
With 1 o 2.5gb WAN port support?
PS: if it's not a problem, can you upload your sysupgrade and factory builds? Just because me (and other) are lazy. Otherwise I'll make my image in the next days.
Thanks!
It's the 1Gbit WAN build
The factory build and the sysupgrade build can be pulled from
and
I have NOT tried the factory build but tested a few times the upgrade and it works just fine - thanks to @boretom and many others on the developing side of the WAX206
1 Like
@giuliomagnifico
At the moment I have installed the factory image from you which you send me for 11 days 
I could now just install the sysupgrade from Fin over it right?
Sorry if a stupid question but I am new and this would be the first time I install a sysupgrade version.
Yes, just install sysupgrade, worked great for me.
1 Like
No, it's not a stupid question - when You're new to openwrt it is a bit confusing all the terms - I'm new to this my self and has done a lot of reading on many of the foras here - I have 3 devices that runs openwrt - all different.
But to Your question : if You're factory build runs fine then perhaps wait until @guiliomagnifico has upgraded the version You got from him - if something is not as expected then he knows how to deal with it and You may benefit from that.
But I think You can upgrade if You feel for it
2 Likes
Of course I will upload my image. It is a little larger with
- FreeRADIUS
- Dawn
- PPPoE (I do not use that so untested)
- OpenVPN
- WireGuard
- and a little more
- No 2.5GBit/s
Works great for me
Edit: Added OpenVPN binaries...
OpenWrt SNAPSHOT r21967+3-097e9bf9d8 / LuCI Master git-23.013.73089-9634086
Factory
Sysupgrade
1 Like
Since I was bored to reinstall all my packages every update with *your (
) images, I just compiled mine but it's very minimal, to use the WAX206 as AP only, it comes without dnsmasq... but with some collectd and Prometheus exporter, because I build lots of stats in Grafana from OpenWrt, example.
If someone want it is here: r21967+openwrt-mediatek-mt7622-netgear_wax206-squashfs-sysupgrade.bin, the .config file is here: https://pastebin.com/PDW2798k
Now if I have some time I can make another image with wan, pope, etc.. I don't remember who need what, just ask (since the Oracle's CPU power is free 
)
Edit: oh, I noticed that I forgot to remove the pppoe packet and support (damn 
) so it has it, if someone needs the pppoe support, it has the support (but remember to install dnsmasq, because I'm sure it doesn't have it).
....and now I have to make another build for me 
Edit2:
Here's the minimal build without pppoe, dnsmasq, etcc... but with collectd, prmometheus exporters, stats,....
Config: https://pastebin.com/nqb23BKr
Build: r21967-AP-openwrt-mediatek-mt7622-netgear_wax206-squashfs-sysupgrade.bin
1 Like
Figured I'd stop by to check on the merge status, seems like it's still some way off sadly.
When building from commit 097e9bf9d842dc20932e85e38f9034ab58f499d9 I eventually run into what appears to be a conflict between different TLS/SSL libraries. Has something about the build procedure changed? I've simply tried doing this again since it seemed to work for people.
Collected errors:
* check_data_file_clashes: Package libustream-wolfssl20201210 wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/lib/libustream-ssl.so
But that file is already provided by package * libustream-mbedtls20201210
* opkg_install_cmd: Cannot install package libustream-wolfssl20201210.
* check_data_file_clashes: Package px5g-wolfssl wants to install file /home/pngu/src/github.com/boretom/openwrt-fork/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/usr/sbin/px5g
But that file is already provided by package * px5g-mbedtls
* opkg_install_cmd: Cannot install package px5g-wolfssl.
make[1]: *** [package/Makefile:70: package/install] Error 255
make[1]: Leaving directory '/home/pngu/src/github.com/boretom/openwrt-fork'
make: *** [/home/pngu/src/github.com/boretom/openwrt-fork/include/toplevel.mk:231: package/install] Error 2
Normally I'd just dig in and figure out how to resolve the conflict, but given that it's not just one, but 3 cryptographic libraries causing trouble on a flavor of Linux I'm not terribly familiar with tells me I should rather ask for help 
Yes, I encoutered the same error few hours ago when I was building my images. I simply deselected the conflicting libraries (in my case was just libustream-wolfssl) but obviously it dependes on your config.
Does the build system, or the KConfig part of it, tell you if something depends on a library you remove? I had a quick browse and found this post about the switch from mbetTLS to WolfSSL which makes me think sticking with the latter might be the better play. Quite frankly though, I have no idea if that's a valid conclusion.