Then under outbound NAT, create your Rule for NordVPN_WG interface, source the IPs you keep private (all if not separating, NAT to NordVPN_WG Address Then Under System->Routing->Gateways, create a new gateway, IP 10.5.0.1, assigned to the NordVPN_WG Interface So from the original instructions, when you create the gateway interface, use 10.5.0.2/29 (I assume everyone is getting 10.5.0.2 as their IP) I figure since this worked I will give my two cents on configuration. OK, I just went through this on PFSense+ 22.01 (Which is free so worth it for more features). So it will be impossible to configure more than one NordVPN client tunnel on pfsense. Both results below are the same serverĮdit: It appears that NordVPN uses the same keys and private IP for every session you have - even on different PC's. It's a bit of mucking around however it's worth it. The only thing I did was change the mask on the assigned ip from a /16 to a /32 I put all this in the relevant section in pfSense it worked perfectly. You should now have all the information you need - your private key and assigned IP. Get your private IP from ifconfig / ip addr depending on your version of linux ![]() Use the WireGuard tools to dump the config ( wg show and wg showconf nordlynx ) ![]() Install NordVPN as per the instructions on their websiteĬonfigure NordVPN to use WireGuard (nordvpn set technology nordlynx)Ĭonnect to NordVPN to your desired server You need a Linux PC so either use an existing one or build a vm However it's relatively easy to extract it (if laborious) For those that use NordVPN, you probably already know that they refuse to provide the required configuration for setting up WireGuard on routers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |