Hi Folks! I wanted to make two related requests that I have been thinking about for a while as a network and security engineer using netmaker. They are both related to the default network creation behavior. The first one which had been bothering me since the pre v0.13 days is the fact that by default every netclient instance creates a tunnel to the netmaker server. Could there be an option when creating a network that tells netmaker to build a mesh without including the server (now that it's not required anymore)? I always disable it manually using acl's but a default option would be cool. Now you might as why I do it that way? The answer being security and using it on k8s. On the server, all the interfaces are routed and could theoretically be used to jump between networks. There is no l3 isolation at the moment. Which brings me to my second request. Including an option for network isolation during network creation. This could mean putting the interface in either a vrf or in more modern terms a network namespace. I am just referring to the server here and not the netclient nodes. Those are a different story. If I were to build a wireguard server to host several independent networks, I would do it using namespaces since wireguard is already namespace aware. Vrf's would work just as well. I just wanted to throw it out there.