Multiple instances wireguard VPN PROTON

Started by FredFresh, June 04, 2024, 06:49:54 PM

Previous topic - Next topic
Hi,

I used to have a working configuration with 3 wireguard Proton VPN isntances (3 different servers) and through a gateway group, I was able to implement a fallback policy.
Note: the gateway priorities were (from top to bottom) wan, server A, server B, server C.
The order in the gateway group: server A, B, C, wan.

Now, after the last updates the system is not working anymore (even after a clean installation and restore of the configuration).

The handshake is done with all the three servers, but only the gateways of the server A has a gateway online.

I followed the officla guides: proton and "road of the warrior" + something else I found online (that I can't find anymore).

WIREGUARD SETTINGS
The 3 wireguard peers have the 51820 ports.
The 3 wireguard instances have:
listen port:51821-51822-51823
dns server: empty (i use a different one)
ip tunnel: 10.2.1.2/32 - 10.2.2.2/32 - 10.2.3.2/32
gateway: 10.2.1.1 - 10.2.2.1 - 10.2.3.1

GATEWAY SETTINGS
gateway ip: 10.2.1.1 - 10.2.2.1 - 10.2.3.1
monitor ip:10.2.1.1 - 10.2.2.1 - 10.2.3.1

the first one is online the tother two are offline.

Please can you help on this?
Thank you

I'm surprised to see that such a configuration worked as when I contacted Proton support I was advised that it was not possible to configure more than one instance as by default the tunnel IP address is always the same 10.2.0.2/32

Would you share more details on your setup?

Tia.

Just for later reference, the problem was the gateway group created that somehow was corrupted. Deleting it and creating a new one with a different name solved the problem.
Creating a GW group with the same didn't solve the problem instead.


Quote from: brionlax on August 05, 2024, 05:30:22 PM
Can you please give us examples of how your firewall rules are setup?
What do you mean and who is us?

Cheers