first thing i'd say is to run 'release' (21.02.1)...
UPGRADEsFLAVOUR="release"
verbage
i'm just not that confident in master at the moment (when it comes to wireguard I also had a failed attempt in the last few days on r17900 but I'm not super familiar with wireguard so was difficult to pin down cause)...
basically at the moment 'stable' means;
the most functional recent master without getting too old
in the RELEASE_NOTES you'll see some comments about potential reported wg issues... which are a good indicator to drop down to 'release' if you require wg, nmap, zerotier...
after you whack on 'release'... then you should probably create a new thread with all the troubleshooting specifics... (the kind of information I posted in the link above)
not sure if I should assign 21.02.1 to everyone on 'stable' although that makes sense in principle given the above issues (if they are proven to be non user-level)...
- users are free to run 'release' at any time...
- alot of people are still getting by on r17900
and current/stable have always been master based... just happens that at the moment... issues are piling up in these...
could be fixed tommorrow but I get the feeling we are likely looking at month/s before master is sufficiently robust across the board... ( have not been able to build it for some time due to wpa-cli missing in action ) (edit: fixed thankyou!)
see: request for help with several issues on master (woohoo this is also now fixed as of r18086)
there is also this: wifi hangs console issue to be aware of for anyone on master using wifi... (edit fixed thankyou! )
there are only 3 key issues i'm aware of on 21.02.1 (not mentioning the packages repo i.e. new or small fixes to packages)
- overlay problem with squashfs (does not effect us)
- auc segfault (does not effect us)
- bootstrap header is aligned left (localfix implemented)
- wifi wont work by default on CM4 WIFI boards (localfix implemented)
- stage2 'out of range' bug (localfix implemented) ( edit: fixed today yay )
- luci docker blk_io_weight bug ( workarounds exist )
- routing repo: naywatch will crash your router
so if you dont install naywatch... all is ok...