![]() ![]() ProtonVPN uses NAT on their end too so why don’t we also use NAT on pfSense to address this problem. Therefore the routing table rejects adding route collisions for multiple Wireguard connections all using 10.2.0.2/32 pointing to multiple different interfaces. The machine would not know where to send the packets if the same network were allow to point to multiple different interfaces. But why does it cause issues? The reason is the routing table. But, this causes issues when you try to use multiple Wireguard connections on the same machine. This is all well and good when you are trying to use one Wireguard tunnel on a single machine. ProtonVPN attempts to preserve privacy by using a single IP address 10.2.0.2 when you connect using Wireguard. We will have to tweak things from this guide but this gives you a good starting point. Please read this first as it will get you up to speed on setting up a single ProtonVPN Wireguard connection in pfSense. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |