I was having problems getting apt install netclient to work. Had to append original netclient entry to /etc/apt/sources.list.d/netclient.list file as only new nmctl entry was there.

Ubuntu 20.04 LTS standard install instructions for netclient

should be corrected now

👍

ok got a new one for you. Can anyone share a redacted wg0.conf file for me, for a standard netmaker client? I'm trying to fabricate one for my truenas and am supposedly making progress, but making the .conf file is pretty new to me.

I'm using this guide and got to the .conf portion. https://www.truenas.com/docs/core/coretutorials/network/wireguard/

hey all i have a quick question if someone can answer please .. i have setup netmaker as a vpn .and clients can download config and i changed the allowed ips to accept all connection ( one setting in wireguard ui in windows ) i would like to run netclient client on linux to do the same .. what flag can i use ? issue is the moment i ran netclient join i lost ssh connectivity to the remote machine i would like netclient client machine ( ubuntu ) to be able to connect to vpn other machines as well i should be able to access it from not-vpn ip i hope i am making sense

hello i am getting the following error when trying to join a network using netclient

[netclient] 2023-01-04 06:29:14 joining my-network at api.netmaker.mydomain.com:443
[netclient] 2023-01-04 06:29:14 network: my-network node my-host is using port 51821
[netclient] 2023-01-04 06:29:14 starting wireguard
[netclient] 2023-01-04 06:29:17 error running command: wg-quick up /etc/netclient/config/nm-my-network.conf
[netclient] 2023-01-04 06:29:17 [#] ip link add nm-my-network type wireguard
[#] wg setconf nm-my-network /dev/fd/63
[#] ip -4 address add 10.100.2.6 dev nm-my-network
[#] ip -6 address add 4307:4206:1234:2::5 dev nm-my-network
[#] ip link set mtu 1280 up dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2:ffff:ffff:ffff:ffff/128 dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2::4/128 dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2::3/128 dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2::2/128 dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2::1/128 dev nm-my-network
[#] ip -6 route add 4307:4206:1234:2::/128 dev nm-my-network
[#] ip -4 route add 194.163.44.146/32 dev nm-my-network
[#] ip -4 route add 10.100.2.5/32 dev nm-my-network
[#] ip -4 route add 10.100.2.4/32 dev nm-my-network
[#] ip -4 route add 10.100.2.3/32 dev nm-my-network
[#] ip -4 route add 10.100.2.254/32 dev nm-my-network
[#] ip -4 route add 10.100.2.2/32 dev nm-my-network
[#] ip -4 route add 10.100.2.1/32 dev nm-my-network
[#] ip -4 route add 10.0.2.0/24 dev nm-my-network
RTNETLINK answers: File exists
[#] ip link delete dev nm-my-network

hello. Amending my request for input. Knowing that NAS's are really normal network appliances, and knowing that TrueNAS is a major network storage tool, I'm curious if anyone has connected their NAS (specifically Truenas) to a netmaker network? Or am I the first? I may have to document my experience if so.

hello Amending my request for input

I seem to be unable to disable the egress nat. When I created the egress i unchecked the nat but the source ip still get overwritten by the egress ip. Here is the flow:

host with ip 192.168.39.22->netmaker egress host 192.168.39.20->netmaker central server->netmaker egress host 192.168.20.2->http server 192.168.20.1

on the http server 192.168.20.1 i see the source ip is 192.168.20.2 instead of 192.168.39.22

is that normal or is that a bug ?

yeah i seem to have the same issue

egress without nat with central relay

now works fine 🙂

Hi, I have mutiple nodes that are on the same subnet 192.168.20.0/24 and I wanna make them all egress nodes so I can access the router in that network. Can this be achived?

Each egress node would have to be in its own wire guard network

so that means exit nodes cant be "HA" right? like running netclient as a deamonset in a k8s cluster only 1 of the pods can? should? be an egress gateway?

Okay, so I'm seeing a persistent issue where nodes that are relayed spontiously seem to revert to being in the mesh directly after a day or so (e.g., there's more than one peer in their config) with no connectivity to the rest of the network. I can restore connectivity if I remove their ip from the relay node, wait a bit and then readd it. This has happened with the last three nodes i've added since the upgrade to 17.1. Any ideas what's going on here?

Okay so I m seeing a persistent issue

Hi, i've been stuck for several days because I can't find any version of netmaker client that fits with the latest version of OpenWrt, which one should I use?

RTNETLINK answers: File exists

Hey, I've noticed that clients are being connected over wlan0 instead of eth0... is there a way to set eth0 as the default?

I've took down all dockers, how come wireguard still show green on my mobile ?

Hello, thank you for your work. It's fantastic. I have a small issue with my server node client. I have a client node on the machine which is running the netmaker server as well. And I do that from the docs “private address from the Netmaker Server” with the udpholepunch no and port outside the range. The problem is I can communicate with the node but it shows as Red Error in the dashboard. Also the dns entries don’t get filled in the /etc/hosts. I believe this is the issue with mqtt communication. But I am not sure how to remedy it. Other nodes work perfectly. (This is 0.17.1)

hi again, im working on a netmaker setup to connect 3 offices each one with a openwrt router all seems fine, 3 nodes got egreess gateway i can ping to eachothers netmaker interfaces and to the eth0 "lan" ips (ie 192.160.1.1, 2.1 3.1) of each router, from any windows machines but cant ping to any windows machines local ips. ie: i can ping to 192.168.2.1 office 2 router interface, but cant ping to 192.168.2.57 windows machine ip. all done from 192.168.1.45 office1windowspc. all windows pc got windows firewall disabled to test the netmaker. can you help me please?

tracert from this pc looks like this:

tracert 192.168.2.57 Traza a 192.168.2.57 sobre caminos de 30 saltos como máximo. 1 <1 ms <1 ms <1 ms office1Router.lan [192.168.1.1] 2 5 ms 5 ms 5 ms office1router.netmaker-vpn [10.0.0.1] 3 office1router.netmaker-vpn [10.0.0.1] informes: Protocolo de destino inaccesible.