edit: seems the reason is that the network i added...
# client
h
edit: seems the reason is that the network i added "disappears" after a restart? but according to "ip a" its there? I can ping it too, and connect to the services on that ip so no problems there? I am kinda confused 😦
b
does /etc/netclient exist?
h
yes it exists with 2 folders and one file, folder is broker.netmaker.#####.tld, config and got a client.key
b
What is in config dir
h
this is the content of the config directory
If i run "netclient daemon" it also shows no networks but if i list the network its there
b
output of journalctl -u netclient
h
it's really weird on my
b
netclient daemon -vvv
h
it's really weird, on normal debian machines it's running fine .
b
try creating a network without a . in the name
h
ok, will try to do that, hold on
b
network names with a "." should not work on normal debian machine either
h
That would make sense but the GUI let me do it so I did. The other network is without a "." in the name. Will try to do it with a "-" then, because we basically got 3 entities who will be managed over the same netmaker instance. But we just did some nameserver changes so i have to wait and try it later. will give you feedback as soon as I got to test it. Thank you very much for your help!
b
Yes, we will need to prevent that
h
Ok It seems to work now. networkname without a ".". But at first it didnt work after a reboot... had to do a "systemctl enable netclient" because it was stopped when i checked for the status with "systemctl status netclient", now its working fine.