There are ways to hack something together based on the config from the proprietary app. The issue is being able to port it to something like an Asus router.NordVPN does not provide configuration information.
Yup. The pip package openpyn developer confirms precisely this here and no, it's not changed.Unless that has changed since last time I checked, NordVPN does not provide configuration information. You are stuck with their proprietary client for the time being.
Double the speed with wire guard would be the main benefit.there is little benefits to using Wireguard instead of OpenVPN from your router when the provider supports both.
Benchmarks run by Asus showed a 50% speed increase in Wireguard vs OpenVPN. And then that speed gets capped at 300 Mbps even when not going through the tunnel due to lack of NAT acceleration. Not a good tradeoff if you have a connection faster than 400 Mbps.Double the speed with wire guard would be the main benefit.
The bottleneck becomes the added CPU load for NAT/routing once you drop NAT acceleration. That caps NAT throughput to around 350 Mbps, which means your WG tunnel traffic would probably cap at around 300 Mbps once you factor everything (such as having one CPU core fully loaded by the NAT software processing).The user should have a choice though if it can be built into the OS on the router. The decreased HW needs for WG should yield better speeds than you're saying since it essentially multithreads the encryption tasks with lower overhead on the CPU.
Well, Nord specifically NAT's the connection prior to any egress into 10.5.0.2 as its GW to the VPN server IP. It's transparent to the PC/devices as it's routing entries in the routing table that force the traffic to take the tunnel path. OPVN creates considerable overhead that will peg a router CPU and result in slower speeds / need for additional cooling.CPU load for NAT/routing
Have you actually tested it on a device that uses your SW?would probably cap at around 300 Mbps
What goes inside the tunnel is irrelevant here. Your encapsulated packets are still sent NATed to your ISP, which then routes them to the remote WG server. So, you still have NAT being done by the router.Well, Nord specifically NAT's the connection prior to any egress into 10.5.0.2 as its GW to the VPN server IP.
Asus engineers tested it when they started working on WG support last spring, they shared their test results with me back then. Those results would be nearly identical with both stock firmware or my firmware. I might have a slight edge on OpenVPN due to the amount of optimizations I've done over the years to my OpenSSL and OpenVPN implementation, but even these are getting closer to being similar these days as I've shared my optimizations with them over the years. With WG I doubt there's anything I could optimize there, except maybe look at possibly improving CPU affinity allocation (which was one of the ways I've improved OpenVPN performance).Have you actually tested it on a device that uses your SW?
It's pretty much the same with virtually any router you can buy out there, outside of high-end enterprise devices, core networking devices, or homegrown x86 devices. Look at business class routers, they generally document the packet throughput in their specs sheet, and they ain't breaking any speed records either.It really doesn't surprise me that even with your slimmed down FW these Asus boxes can't handle the VPN side.
I figure hooking up a GIG WAN connection and GIGI LAN it should be able to hit speeds similar to a direct connect to a PC but it only hit about 25% of the line speed w/o anything enabled on the Asus that would have caused the slow speeds / performance.
lspci
00:00.0 Host bridge: Intel Corporation Device 4668 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
00:06.0 PCI bridge: Intel Corporation Device 464d (rev 02)
00:08.0 System peripheral: Intel Corporation Device 464f (rev 02)
00:14.0 USB controller: Intel Corporation Device 7ae0 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7aa7 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 7acc (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7ae8 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 7ae2 (rev 11)
00:1a.0 PCI bridge: Intel Corporation Device 7ac8 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7aba (rev 11)
00:1c.3 PCI bridge: Intel Corporation Device 7abb (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab0 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a84 (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7ad0 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7aa3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 7aa4 (rev 11)
01:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN850 (rev 01)
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN850 (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
05:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:02.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:03.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:08.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:0a.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
06:0b.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01)
08:00.0 Ethernet controller: Aquantia Corp. AQC111 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
09:00.0 Ethernet controller: Aquantia Corp. AQC111 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
0b:00.0 Ethernet controller: Aquantia Corp. AQC111 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
0c:00.0 Ethernet controller: Aquantia Corp. AQC111 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02)
sudo inxi -F
System: Host: server Kernel: 5.17.0-051700rc5-lowlatency x86_64 bits: 64 Console: tty pts/1
Distro: Ubuntu 21.10 (Impish Indri)
Machine: Type: Desktop Mobo: ASRock model: Z690 Steel Legend serial: HQ0210001702488 UEFI: American Megatrends LLC. v: 2.02
date: 10/01/2021
CPU: Info: 10-Core model: 12th Gen Intel Core i7-12700K bits: 64 type: MT MCP cache: L2: 25 MiB
Speed: 600 MHz min/max: 800/6300 MHz Core speeds (MHz): 1: 600 2: 600 3: 599 4: 601 5: 1655 6: 4151 7: 803 8: 2606
9: 800 10: 800 11: 800 12: 802 13: 618 14: 894 15: 939 16: 601 17: 1032 18: 801 19: 609 20: 600
Graphics: Device-1: Intel AlderLake-S GT1 driver: i915 v: kernel
Display: server: X.org 1.20.13 driver: loaded: fbdev unloaded: modesetting,vesa tty: 202x55
Message: Advanced graphics data unavailable in console for root.
Audio: Device-1: Intel driver: snd_hda_intel
Sound Server-1: ALSA v: k5.17.0-051700rc5-lowlatency running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.32 running: yes
Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169
IF: enp3s0 state: down mac: a8:a1:59:7a:82:f0
Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
IF: wlp4s0 state: down mac: d8:f8:83:d8:8e:c0
Device-3: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion] driver: atlantic
IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: 24:5e:be:4d:c4:53
Device-4: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion] driver: atlantic
IF: enp9s0 state: up speed: 2500 Mbps duplex: full mac: 24:5e:be:4d:c4:54
Device-5: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion] driver: atlantic
IF: enp11s0 state: up speed: 1000 Mbps duplex: full mac: 06:7e:4e:62:3b:e3
Device-6: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion] driver: atlantic
IF: enp12s0 state: up speed: 1000 Mbps duplex: full mac: 06:7e:4e:62:3b:e3
IF-ID-1: bo0 state: up speed: 2000 Mbps duplex: full mac: 06:7e:4e:62:3b:e3
IF-ID-2: bonding_masters state: N/A speed: N/A duplex: N/A mac: N/A
IF-ID-3: br0 state: up speed: 2500 Mbps duplex: unknown mac: 5a:ea:69:a9:d9:fb
IF-ID-4: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth: Device-1: Intel type: USB driver: btusb
Report: hciconfig ID: hci0 state: up address: D8:F8:83:D8:8E:C4 bt-v: 3.0
RAID: Device-1: md0 type: mdraid level: raid-10 status: active size: 18.19 TiB report: 5/5 UUUUU
Components: Online: 2: sdb1 3: sdd1 4: sda1 5: sde1 6: sdc1
Drives: Local Storage: total: raw: 38.21 TiB usable: 20.01 TiB used: 8.2 TiB (41.0%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB
ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB
ID-3: /dev/sda vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB
ID-4: /dev/sdb vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB
ID-5: /dev/sdc vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB
ID-6: /dev/sdd vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB
ID-7: /dev/sde vendor: Western Digital model: WD80EZAZ-11TDBA0 size: 7.28 TiB
Partition: ID-1: / size: 915.77 GiB used: 107.56 GiB (11.7%) fs: ext4 dev: /dev/nvme0n1p2
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 33.0 C mobo: 38.5 C
Fan Speeds (RPM): fan-1: 770 fan-2: 838 fan-3: 0 fan-4: 780 fan-5: 0 fan-6: 0 fan-7: 743
Info: Processes: 473 Uptime: 12h 58m Memory: 15.39 GiB used: 3 GiB (19.5%) Init: systemd runlevel: 5 Shell: Bash
inxi: 3.3.06
ip r
0.0.0.0/1 via 10.5.0.2 dev nordlynx
default via WAN GW dev bo0 proto dhcp src WAN IP metric 208
WAN CIDR dev bo0 proto dhcp scope link src WAN IP metric 208
128.0.0.0/1 via 10.5.0.2 dev nordlynx
169.254.0.0/16 dev lo scope link metric 1000
172.241.224.41 via WAN GW dev bo0
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.1
I still stand by my comment in https://www.snbforums.com/threads/wireguard-and-nordvpn.77685/post-748717 . If running it on a router, use OpenVPN (or IPSEC). If running it on a PC, then you may consider WireGuard.@Tech Junky @RMerlin - I stumbled upon your discourse and enjoyed it but felt it was unresolved... any updates?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!