Live data from Hacker News

NetMaker: Connect Everything with a WireGuard VPN

netmaker.io

61–70 of 172 posts

Re: NetMaker: Connect Everything with a WireGuard VPN

#61

Related, from earlier this year: https://news.ycombinator.com/item?id=35584533 Wherein the author compares Yggdrasil, tinc, Tailscale, Zerotier, Netmaker, Nebula, and ends up prefering Yggdrasil. Actually, it was this comparison that made me look into Netmaker and prefer it and I've been running it without issue for experimentation. I hope the author revisits NM. I agree that the project is moving quickly, which resu…

> route coordination After reading the readme on the Github, it's still not clear to me whether it proxies everything through its own servers or not

Not when using the selfhosted version https://www.netmaker.io/pricing

Re: NetMaker: Connect Everything with a WireGuard VPN

#62

Related, from earlier this year: https://news.ycombinator.com/item?id=35584533 Wherein the author compares Yggdrasil, tinc, Tailscale, Zerotier, Netmaker, Nebula, and ends up prefering Yggdrasil. Actually, it was this comparison that made me look into Netmaker and prefer it and I've been running it without issue for experimentation. I hope the author revisits NM. I agree that the project is moving quickly, which resu…

The use of relays is common when you connect to the VPN in the enterprise networks that often allow only outgoing 80/443. Also, you may not use the relays all the time, but you may use them sometimes throughout the day. If there is a vulnerability, one connection may be enough to compromise the security.

Re: NetMaker: Connect Everything with a WireGuard VPN

#63

This thing seems to open a whole lot of attack vectors in addition to wireguard's ports. Is it worth it?

if you can point out the vectors that worry you maybe other will be able to address them sooth your worries

Wireguard requires an open UDP port, by default 51820.

NetMaker, at least based on the quick install manual, asks you to open up the following:

- 443, 80 (tcp)

- 3479, 8089 (TURN, TURN api)

- 8085 (exporter EE)

- 1883, 8883, 8033, 18083 (if using EMQX)

But perhaps none of these are required for actual WAN/Wireguard connections and one needs only limited access to these ports in order to configure the software.

Re: NetMaker: Connect Everything with a WireGuard VPN

#64
post #20

it's going to need a comparison page i already have tailscale setup on all devices

This article (titled "Tailscale vs ZeroTier") actually compares Tailscale, ZeroTier, and Netmaker: https://www.netmaker.io/resources/tailscale-vs-zerotier

The quality of information is very limited. It's as if the author hasn't used ZeroTier...

ZeroTier operates on a different layer, and is therefore capable of much more than anything wireguard.

Re: NetMaker: Connect Everything with a WireGuard VPN

#65
post #26

Earlier quoted context omitted.

Is the kernel module how they claim the 5x performance over tailscale? I haven't really done any real tailscale performance metrics but can't see how else they can claim this (unless there is infrastructure performance differences).

Afaik, tailscale recently made changes to their go user space implementation that actually made their version faster than the kernel implementation, at least in some cases. I remember reading a blog post on tailscacles' website about it and how they are pushing their changes upstream (wg kernel and official wg go user space implementation). Can't find the post now though.

Go is a bit too slow for performant networking - not sure why people are hell-bent on forcing it into such spaces where it doesn't fit.

Re: NetMaker: Connect Everything with a WireGuard VPN

#66

Earlier quoted context omitted.

if you can point out the vectors that worry you maybe other will be able to address them sooth your worries

Wireguard requires an open UDP port, by default 51820. NetMaker, at least based on the quick install manual, asks you to open up the following: - 443, 80 (tcp) - 3479, 8089 (TURN, TURN api) - 8085 (exporter EE) - 1883, 8883, 8033, 18083 (if using EMQX) But perhaps none of these are required for actual WAN/Wireguard connections and one needs only limited access to these ports in order to configure the software.

i use fireguard through tailscale to access multiple machines over ssh, with their setup i was able to reduce exposure as i no longer need to open a port on the router

tailscale does this with their DERP servers

i doubt netmaker doesn't have an alternative to connect machines behind nat routers; that would be a serious disadvantage for soho setups

Re: NetMaker: Connect Everything with a WireGuard VPN

#67

Earlier quoted context omitted.

Dormant, or stable? I've been running a tinc mesh network for eons w/ my systems and it's never given me any trouble. I use git to check in the 'hosts/' folder and add/remove hosts as needed, pull down to all the nodes, and they can all connect. I do wish the encryption + transport could be as performant as wireguard, but for my needs, I haven't been pushing it hard enough that it's a concern for me.

Tinc works, but is not really stable for my use case: strange network environment thanks to my school. It frequently falls into infinite loops, dropping all packets and fully use a CPU core (on Windows, Linux looks fine). It seems stable on an all-Linux network, but the moment a Windows client is added, things can go wrong. It also does not really have a decent mobile client.

Thats very strange. I use tinc-vpn exclusivly for my network. Both Linux, Win32, and FreeBSD. Everything is very stable.

But I have to admit, I have private fork of tinc-vpn specifically for Win32. AFAIR I did only minor changes to TAP driver initialization and how scripts are executed. They have they own thread now and additionaly there is script called tinc-pre to handle IP initialization before TAP interface is up. Becuase meh, Windows Network Interfaces work strange :)

Re: NetMaker: Connect Everything with a WireGuard VPN

#69

Earlier quoted context omitted.

Tinc is dormant these days. Very little development going on. Cool concept, but limited performance and limited uptake. Their approach to mesh was neat at the time.

Dormant, or stable? I've been running a tinc mesh network for eons w/ my systems and it's never given me any trouble. I use git to check in the 'hosts/' folder and add/remove hosts as needed, pull down to all the nodes, and they can all connect. I do wish the encryption + transport could be as performant as wireguard, but for my needs, I haven't been pushing it hard enough that it's a concern for me.

Same here. Im very happy with tinc-vpn. It can easly push 100Mbit traffic through my severs and thats enough for my needs. Also, auto-mesh is very nice feature. I do NOT want to forward traffic via my central hubs.

Note: I use tinc-vpn only in switch (L2) mode. For routing good old quagga (forked) does it job.

Re: NetMaker: Connect Everything with a WireGuard VPN

#70

Related, from earlier this year: https://news.ycombinator.com/item?id=35584533 Wherein the author compares Yggdrasil, tinc, Tailscale, Zerotier, Netmaker, Nebula, and ends up prefering Yggdrasil. Actually, it was this comparison that made me look into Netmaker and prefer it and I've been running it without issue for experimentation. I hope the author revisits NM. I agree that the project is moving quickly, which resu…

> Docs are written for self-hosters. These are all good signs.

Except at the time of writing, netmaker isn't FOSS: https://github.com/gravitl/netmaker/blob/16d5b5807/LICENSE.t...

Post reply on HN