yep, a bit like I did in the past using mikrotik and eoip, although that just gave awfull speeds

Yes, this is exactly one one of the usecases that netmaker is designed to solve

🙂

@User Sorry I just saw this. Let me know if you run into any problems setting up and we can do a session.

@User thanks, will probably continu configuring this tonight, will let you know if I ran into any issues and we can indeed do a session, thanks for the offer!

I just installed it using client mode but in contrary of the video I do not have a default node already installed?

default nodes No nodes present in network: default...

that was as easy as setting one up haha

What logs did you get from the server?

I just tried a iperf test before Im going to toy with creating some layer2 part and I can actually use up my entire internet bandwidth between the 2 wg endpoints which is quite awesome actually 😄

root@wg-netmaker:~# iperf -c 192.168.2.9 ------------------------------------------------------------ Client connecting to 192.168.2.9, TCP port 5001 TCP window size: 153 KByte (default) ------------------------------------------------------------ [ 3] local 10.10.10.1 port 46902 connected with 192.168.2.9 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 574 MBytes 480 Mbits/sec nice! so, should I just add a nic to the netmaker vm now, bridge them and we're off to the races?

can you describe your layout a little more for what you are trying to accomplish?

Also @here wanted to mention the big goals for the next release (hopefully by week after this one): 1. IPv6: Allo IPv6 endpoints as well as dual stack IPv4 and IPv6 private addresses for networks 2. Private DNS: Optional Private DNS server via CoreDNS. Default DNS mapping of node name to private IP, and then you can add entries for whatever you'd like in your network.

I first need to solve something else lol as it seems in someway without me doing anything it went haywire

Netmaker: 6: nm-default: mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.10.10.1/24 scope global nm-default valid_lft forever preferred_lft forever inet 10.10.10.3/24 scope global secondary nm-default valid_lft forever preferred_lft forever inet 10.10.10.2/24 scope global secondary nm-default valid_lft forever preferred_lft forever Home: 3: nm-default: mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.10.10.2/24 scope global nm-default valid_lft forever preferred_lft forever inet 10.10.10.1/24 scope global secondary nm-default valid_lft forever preferred_lft forever inet 10.10.10.3/24 scope global secondary nm-default valid_lft forever preferred_lft forever

why the hell would it do that and more importantly, how do I fix that? Already tried restarting the netclient

@User I'm trying to build a sort of layer2 between home and DC so that I can put virtual machines on a home IP without needing yet another server at home 🙂

tried it with mikrotik eoip at some point but that was just horrible speeds, speeds I got with wg now blow that out of the water

that is strange....I have not seen that before. Did you attempt multiple installs? The only way it could have gotten 3 addresses is to partially install, fail, fail to uninstall, then install again

only 1 install of the netclient on both machines

quick fix would be to just run netclient -c remove -n default on the server to remove interface and then netclient -c install -n default -t to re-add it

what do you have under /etc/netclient?

let me see

root@dbc-gateway:~# cat /etc/netclient/ netclient netconfig-default nettoken-default wgkey-default

once removed should I use the full line again including the netclient install?

4: nm-default: mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.10.10.1/24 scope global nm-default valid_lft forever preferred_lft forever back to one on my home one, let me do the other side as well

very strange...in the UI/API, do you see multiple instances?

I think I know how this happens now

as I could reproduce this

what happened?