wireguard | Manage/Install WireGuard on applicable ASUS routers | VPN library

https://github.com/Nyr/wireguard-install/blob/master/wireguard-install.sh#L15

Indeed, this is a bit problematic. Typically, not caring, you would just:

I've been really racking my brain with this problem for a long time. After researching a lot I ended up discovering that in my case, this same problem was due to the network MTU.

I solved it by just lowering the MTU directly on my WSL distribution. If you don't use a linux distribution, you can just try to change it directly through the router. (Decreasing or increasing until it works)

I've figured it out, Tshark gave me a hint with the TCP Retransmission errors, reverse searching that on google reveals that MTU settings might be at fault and indeed that was the issue, setting the MTU correctly in Wireguard has resolved this issue

The wg-quick script sets up these rules only when you configure the AllowedIPs of a WireGuard peer to include /0 -- aka "all addresses" or the "default route" for an address family (0.0.0.0/0 for IPv4 and ::/0 for IPv6).

Using a tunnel like WireGuard for a default route requires some tricks to work correctly in most scenarios. The main trick wg-quick uses is to put the new default route into a custom routing table, while adding policy routing rules with a firewall mark to overide only the default route of the main table. This is the purpose for the route and policy rules you'll see wg-quick set up in this case:

Something like this

Ok, I figured it out -- there's three parts to this:

I may have missed QTS version on your configuration. Do you mind giving us a few details? Wireguard means a fairly recent version, but which one is important.

I recently updated a new NAS to QTS 5, and a perfectly working OpenvPN server stopped working altogether. Worked like a charm in version 4, being overzealous in updating the server was (sadly predictably) a mistake. Concrete result is, I now get an infinite timeout on port 1194, which ends up with "TLS handshake failed".

Same situation after dropping the OpenVPN configuration on the NAS and recreating it from scratch. So the answer to your problem may be as simple as having to wait for QNAP to fix either QVPN or LAN management on QTS 5.

Unfortunately I cannot access the NAS remotely anymore, so I can't corroborate your feedback that Qbelt is not affected. I will have a TeamViewer set up on the LAN tomorrow ta get access to the NAS again, and I'll give it a try.

You need to understand getRandomValues is on window.crypto that means it works on browser. To make it work on Node.js you need to install get-random-values

It depends on what do you want to protect. For protecting all communication between two machines use a VPN like Wireguard. For protecting the communication of a single service use TLS.