Hmm, I think I've stumbled upon some issues caused by netclient. I noticed a node running pop-os was very sluggish and saw that systemd-resolved caused 100% cpu load. Checking the logs I could see that it complained about invalid arguments in /etc/hosts

Sep 10 11:07:12 pop-os systemd-resolved[3857]: /etc/hosts:670: address 'backer' is invalid, ignoring: Invalid argument
Sep 10 11:07:12 pop-os systemd-resolved[3857]: /etc/hosts:676: address 'on' is invalid, ignoring: Invalid argument
Sep 10 11:07:12 pop-os systemd-resolved[3857]: /etc/hosts:2143: address 'ker' is invalid, ignoring: Invalid argument
Sep 10 11:07:12 pop-os systemd-resolved[3857]: /etc/hosts:2148: address '0.100.1' is invalid, ignoring: Invalid argument
Sep 10 11:07:12 pop-os systemd-resolved[3857]: /etc/hosts:2154: address '100.1' is invalid, ignoring: Invalid argument

Upon further inspection I noticed that /ets/hosts was over 300MB large (~16M lines) and the first ~2000 lines are full of "#" and these odd line breaks... After that the remaining million rows are "more" correct, but the netmaker network is just called "nm-". The last part of hosts is looking correct with nm-mynetwork. Any clue what might have caused this madness? 😄