try deleting the netclient folder en reinstall, that worked for me

Hi again, I'm running into the issue where netclient sets the route to the eth interface that has no internet access. It's using eth1 rather than eth0 in my case. This seems to happen in the

routes_linux.go

file. If I run

ip route show default

the first line shows the correct interface first and according to the code it should pick that one. Is the output from

ip route show default

randomized perhaps?

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? 😄

Aha, found https://github.com/gravitl/netmaker/issues/1184 and my node has first letter in capital..

Can't seem to edit the network to change name either 😐

Key: 'Network.NetID' Error:Field validation for 'NetID' failed on the 'netid_valid' tag
[netmaker] 2022-09-10 09:28:22 pellen failed to update network:  Key: 'Network.NetID' Error:Field validation for 'NetID' failed on the 'netid_valid' tag
[netmaker] 2022-09-10 09:28:22 processed request error: Key: 'Network.NetID' Error:Field validation for 'NetID' failed on the 'netid_valid' tag

Network name is not editable

Ok, so I should re-create it instead with only lower case?

Yes

[netclient] 2022-09-10 17:20:43 error setting route for netmaker: exit status 2 what would be the reason for getting that in the client? I got it now in Debian 11 and Ubuntu 20

Hi everyone, i am having issues with my netmaker deployment. So my situation is that i am able to ping from node to node. But i cant ping or get access to nodes from my external clients. All pings are having request timeout errors. I have tried everything and red trough all the documentation but i am not able to figure this thing out. I am at the point of loosing my mind and i bet this can be solved but i dont know where to look for solution any more. You guys are my last resource... 😦

I still cant get to ingress client to stop being "NATed" behind the ingress server (also acting as the netmaker server-docker). RCE=on and postup/down has masquerade command removed as advised but I Ext-Clients are still NAT behind the servers IP. Inside the netmaker docker I see: iptables -t nat -S -P PREROUTING ACCEPT -P INPUT ACCEPT -P OUTPUT ACCEPT -P POSTROUTING ACCEPT -A PREROUTING -p tcp -m tcp --dport 53 -j DNAT --to-destination 172.21.0.3:53 -A PREROUTING -p udp -m udp --dport 53 -j DNAT --to-destination 172.21.0.3:53 -A POSTROUTING -j MASQUERADE

I have a docker node set up that i want to egress out of to the network that the docker host is on. I have tried "eth0" which is the interface where the machine that docker is running on is connected to but it doesn't work.

Hi can anyone help me on my way? If got this network. Netmaker is working fine (flying). Trying to join a new client. Netclient (v0.15.2) is installed and working under systemd: ● netclient.service - Netclient Daemon Loaded: loaded (/lib/systemd/system/netclient.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2022-09-16 12:03:16 CEST; 8s ago Docs: https://docs.netmaker.org https://k8s.netmaker.org Main PID: 779 (netclient) Tasks: 9 (limit: 11897) Memory: 5.8M CPU: 31ms CGroup: /system.slice/netclient.service └─779 /sbin/netclient daemon I enter my key: sudo netclient join -t -vvv That returns the shell: [netclient] 2022-09-16 12:04:35 joining hak8s at api.netmaker.n-able.consulting:443 [netclient] 2022-09-16 12:04:35 error installing: error creating node 500 Internal Server Error {"Code":500,"Message":"Key: 'Node.LocalAddress' Error:Field validation for 'LocalAddress' failed on the 'ip' tag"} [netclient] 2022-09-16 12:04:35 error running command: wg-quick down /etc/netclient/config/.conf [netclient] 2022-09-16 12:04:35 wg-quick: `/etc/netclient/config/.conf' does not exist [netclient] 2022-09-16 12:04:36 removed systemd remnants if any existed I have a high-available setup, where I come in over a load balancer. I can figure out which netmaker vm, and which netmaker apps on the vm in docker are involved. But I am hoping someone is familiar already with this issue before I spend my time diving in.... As far as I can asses api.netmaker.n-able.consulting is not the issue, this is a local netclient 500 error or is api.netmaker (server side) giving this back an error 500. Is anyone able to help me out with what is going on here?

v0.15.2

hi all Can any one help or reflect. Earlier today I had problems adding a new client to my service mesh. My mesh was ok at that time. See the picture with the blue dots (only one laptop, not online red). It turned out that I could not add the client due to changes made between version 0.15.0 and 0.15.2. So I was adviced to upgrade all netclients and my netmaker servers to version 0.15.2. All went well (I changed all image tags on the serverside to latest), without hassel. But then I noticed that my service mesh (k8s cluster) nodes all accept for my netmaker servers had become red & I do not see the netclient upgraded versions in the nodelist. See the second SM picture. Netmaker is working fine, my clusters is running ok, so no wireguard misconfigurations. See also traffic over my Loadballancers going to all netmaker endpoints. But except for the netmaker servers all is red. How to

Finding this in netmaker logs:

[netmaker] 2022-09-16 13:00:44 error unmarshaling payload invalid character 'v' looking for beginning of value [netmaker] 2022-09-16 13:01:41 error updating node w4 30a5b210-6cdb-4270-a952-e0f53ee4c104 on checkin Key: 'Node.Connected' Error:Field validation for 'Connected' failed on the 'checkyesorno' tag

[netmaker] 2022-09-16 13:29:38 error updating node w2k1000 b0a0b557-9e6f-45fa-a192-f885ae23c079 on checkin Key: 'Node.Connected' Error:Field validation for 'Connected' failed on the 'checkyesorno' tag [netmaker] 2022-09-16 13:29:53 error updating node m4k1000n-ablehosts 34cf1c4a-3f09-477f-92fc-aa983064c038 on checkin Key: 'Node.Connected' Error:Field validation for 'Connected' failed on the 'checkyesorno' tag

on each node that is red run

netclient disconnect -n <network-name>; netclient connect -n <network name>

done. all is directly blue again..... 🙂

Thanks!

does the docker netclient work with egress gateways? for me it didnt work but the regular client worked just fine?

Is there any documentation on how to use the netclient docker image? Either I am blind and can't find it or there is nothing? I want to run it on a truenas scale machine to join that machine into a network :X

Hello, I have two linux nodes in a network. One is an egress node, both nodes are able to ping each other, but when I try to ping something on the egress network from the non-egress node, it keeps trying to route out through it's own local network. Any ideas? Am I missing a setting? The egress network IP range does not match the local network of the non-egress node.

I'm on 15.2

Hi, I am having an issue with net client when trying to join a network I am getting the following error : « error installing : error creating node 500 internal server Error {Code:500, « Message :Key: ‘Node.LocalAddress’ Error: Field validation for ´LocalAddress’ failed on the ´up’ tag }

Hm the server is 15.1 and client 15.2

To my knowledge miner version should be compatible….

Thanks @bored-island-21407 your right seems like client and server must be in same version