Wireguard Server/Client no longer works.

Routers VPN, DNS, Leaks
1

I have 2 AXT1800. I set one as a server and other as a client.
I setup portforwarding... and it worked.
Next I had another GL router and also setup as a client.
Both clients were working fine yesterday.

Today both clients stopped working. They were unable to connect to Wireguard server.

I did many tests to get it to work again. Below steps were taken

  1. removed Wireguard clients... resent config files from Wireguard server
  2. Removed port forwarding from IP router
  3. Updated port forwarding to 51825. When I updated portforwarding I noticed that wireguard clients with old port 51820 yellow in GLI Amin panel. This told me that GLI is successfully connected to ISP router.
  4. Updated travel router LAN to 192.168.12.1
  5. Installed PC Wireguard app. Added tunnel and log displays "Handshake for peer 3 (My IP:Port) did not complete after 5 seconds, retrying
  6. Stop/Start Wireguard server then try to start Wireguard client
  7. Enable/Disabled DDNS and sent new config files.
  8. Updated MTU to 1400
  9. Unplugged/plugged both ISP & GL routers.

When I setup port forwarding... GL router does seem to connect to ISP router. I know this because when I updated port number from 51820... any clients with port 51820 were yellow in GL Admin Panel.

I would greatly appreciate any assitance.

Thanks.

2

Hi,

Please confirm whether GL router or ISP router have a public IP (not CGNAT, even public IP is dynamic).

4

Hello Bruce.

GL router does not have a public IP. The IP address for GL router is 10.0.0.21

IP address for ISP does have a public IP.

Note: ISP IP address did seem to change after I restarted ISP router. One of the final tests I was doing... was installing Wireguard PC app on my PC... and viewed log file... Viewing log file, I noticed the IP was different... checked ISP router IP... and confirmed it was the same IP but it had changed... This is how I noticed ISP IP had changed.

I am using a GL travel router as a Wireguard server... but in your documentation... I saw you had a home router Flint 2 running as a server. I purchased the Flint 2 to use as the server. Once I receive I will try again and update you.

Since it was working I understand that I should not purchased the Flint 2, but ran out of ideas. Since I already purchased... might as well wait for it to arrive and continue testing.

Let me know if you would like to know any other information.

Thanks.

5

You can enable DDNS function on the GL VPN server router, and you will no longer worry about changes in public IP.

Since it is working normally, you don't need to buy Flint2.Of course you can also wait for delivery. Flint 2 is as a Home VPN server and Travel router to take with you on the go.

7

FYI,

I initially enabled DDNS function on the GL server router. But since it stopped working, that is why I had disabled & enabled DDNS in GL server router. Every time I made any changes I would always downloaded new config files.

Since it is working normally, you don't need to buy Flint2.
It is not working normally. This is why I decided to buy the Flint2 and also decided to write here :slight_smile:

I should receive Flint2 this Friday... I will get back to confirm if I still have an issue.

1 Like