i can try ^^ though I really can't write sane GO, I'm mostly a python bear :P The PR on the otherday was possible since it wasn't much of a go problem but just systemics

our philosophy is sort of that the netclient acts as a configure-er for the tunnels, but that they should be functional without the netclient being involved

hm, okay - that is a fair question then

personally I would not want any tunnel running without a netclient that configured it other than a external client

yeah that's fair, we'll have to think about this a little bit. But at the very least we could add a function to call after shutting off the daemon (netclient stoptunnels or something)

I know this may seem kind of unconventional, but would it be possible to access multiple networks from one netclient, or have more than one netclient instances on the same computer? I also need to be able to run exit nodes, but since each node is on an identical subnet, with the same IP addresses, is there any way to map the IPs in a subnet to unique IPs on the netmaker side?

Yes, you can join multiple networks from one netclient. Just run join again

cool. How would i remap exit nodes with identical subnets to unique IP addresses?

No easy way to do that. Even on a virtual network, you can't have the same IP on multiple machines.

They would have to be on separate networks

On an egress gateway, instead of entering a whole subnet, could I just enter several IP addresses on my "unique subnet" and then use IPtables on the client to map the addresses form the "duplicated subnet" to addresses on the "unique subnet" ?

Yes, you could try that

Is there a reason netmaker uses a different MTU than default?

1420 is the default wireguard mtu

NM configures 1280

In a good percentage of environments 1420 is too high, we’ve found that 1280 prevents that from happening. A few tools like Tailscale use this as well. But you can change the network default by editing the network

okay :)

Hi! I have a question regarding netmaker/wireguard and QoS. Quick summary: we have a network of devices that are connected to a router where we want certain traffic going in and out of the router to be prioritized. We also want these devices to be accessible to other clients in the netmaker network. My initial idea was to have it so that all of the devices that are connected to the router talk to the router without wireguard so that the router can do its QoS normally. Then the router itself will encrypt the network traffic and send it over wireguard to the netmaker network, exposing these devices to the rest of the netmaker network. However, the issue I've run into is that I haven't found a good way to expose the devices connected to the WG-enabled router to the rest of our netmaker network. I read the docs and saw that maybe what I want is an egress gateway, but to have an egress GW on the router I would have to install netclient on the router itself (which I suppose is not really possible due to the OS on the router). So, does anyone have any suggestions as to how to achieve this kind of QoS in a netmaker setup? 🙂

what OS are you running on the router?

It's a Teltonika RUT240. Which, I just realized that it seems like it is running some modified version of OpenWRT

So I suppose I might be able to install netclient on it after all, just not with the regular command

Seems like that repo only provides netclient for x86-64? The arch on the RUT240 is MIPS 24KC. Can I use any of the releases in the netmaker repo for this arch?

it's always windows lol

Hello, I've finally got a Netmaker network up and running but I'm facing some strange behavior in connectivity between peers. My Setup is the following: * 2 real servers in different data centers running Proxmox VE. Both servers are running netclient. * each server provides 3 VMs which shall be able to talk to each other to form a HA k3s cluster. The VMs run behind NAT in subnet 192.168.0.0 * 1 Netmaker Server Node running publicly on EC2 With a basic mesh setup only the 2 bare-metal host servers can reach every peer. Peers can only reach other peers within the same data center. (Yes, I activated UDP hole punching). So I thought I make both host servers a relay node each for the VMs running on them. This ended up looking like the first picture. Thing is... that now only the 2 Relay Servers were able to reach each other and that's it. Now the fun part... If I only make one of the 2 servers a relay server like on the second picture, everything works like a charm. And it doesn't matter if aio1 or aio2 is the relay for their VMs. It's kinda mutually exclusive. Both as relay don't work. None as relay doesn't work but a single one works. It's a bit odd. Has someone of you faced something similar or am I missing something obvious here?

hmmm I have a theory about this. Can you show the output of "wg show" when there are 2 relays?

which peer is this from?

(also deleted message bc it has sensitive info)

oh, that was from aio2 (the 2nd bare metal server facing public)

publickey: jMqbbFY7BKZm1A6QDUvsJ1zB1NURTSW0buY