Brume 2 - cannot connect VPN client to server

Technical Support for Routers
1

I have had it up to here with this - been working on this for close to 7 hours without headway

I have 2 WireGuard VPN clients in another city. They cannot establish a VPN connection to the VPN server here.

I have reset the server here and attemped to reinstall the setup from before knowing I have to redo the config files for the others via GoodCloud.

I have set a static IP on the Brume to 1.32 and left the port the default 51820. I have a desktop plugged into the Brume and it gets an 8.136 IP with the gateway set to.8.1.

On 3 different routers (TP Link Deco M5, Linksys Velop, and Synology RT6600ax) I have setup port forwarding to send traffic to those ports to the 1.32 IP. I cannot ping 1.32 from other systems on the network unless I put the Brume 2 into bridge mode. If I do that, I cannot use it as a VPN server because I don't have those options available.

When I go to port checker, it says that port 51820 is closed. Port forwarding on the rt6600ax points to 51820 and to the 1.32 ip.

Modem is a standalone Motorola MB7811. ISP is Comcast.

HELP!!!! I am cracking up on this one. It used to work.

2

Please read How to troubleshoot WireGuard carefully.

3

I did. I spent 8 hours going back and forth over it. In the end and despite port forwarding showing up as closed and the IPs shown in GoodCloud not matching up as the same as Brume 2 VPN server, I was able to confirm that it was indeed working. I am used to the system showing the same IP as the VPN server when it is connected and working.

When I have a connected device visit icanhazip.com and whatitmyIP.com, the clients are showing the IP and location as the VPN server. That is all that matters there. Maybe things will start working where it shows the IP of the VPN clients and the server are the same sometime in the future.