Bug found on offline gateways for wireguard...i believe

[FredFresh]

I have 3 connections to proton vpn through wireguard (installed through the official guide and the minimum tuning on the instances to have multiple connections) , everything works in the beginning, after some weeks it stop working (offline gateways and after sometime also no handshake)

I tried fully fresh installation....same story as above.

After restarting the modem (chaging ip from isp), the connections were able to handshake again, but still not connecting (gateways were still down).

After starting ping and traceroute to the gateway addresses (one at time), one after the other the gateways returned up and everything was working again.

If needed, please tell me what information I can provide on this to help investigations.

UPDATE: PROTON confirmed that they have no policy on banning users IP.
After the last tests, once all the 3 connections don't work anymore, it is enough to reset the modem and perform procedure mentioned above to ahve again all the three VPNs working again.

[FredFresh]

Hello, just now i found the 3 vpn notworking, restarted the modem, and pinged+tracerout in parallel to the gateway ping of each one reported the connections UP.

[not_the_messiah]

Hi there!

I'm trying to setup multiple ProtonVPN WG connections to add to a Gateway Group, but I cannot get it working correctly - would you be able to share your setup?

Thanks!

[FredFresh]

Hi, you can follow this https://docs.opnsense.org/manual/how-tos/wireguard-client-proton.html
and
set the PEERS as described in the manual
but
set the instances with ports 51820, 51821, 51822 / tunnel address 10.2.0.2/32 , 10.2.1.2/32, 10.2.2.2/32 / gateway 10.2.0.1 , 10.2.1.1, 10.2.2.1 (all these parameters must be unique).