Wireguard on Flint2 after 4.7 update

Hello. I had set up a wireguard server on my flint 2 so I could access my lan when I'm away from home. Primarily to access Plex, jellyfin and my Sunshine gamestreaming server. I updated to the latest firmware and it seemed to have nuked my wireguard. It just stopped working. I reset my router and tried to set it all up again but I am having issues.

First issue I can see is that my DDNS is not working. The inbuilt DDNS test comes back as working, but I try to access the website, I get an ERR_CONNECTION_TIMED_OUT. Even when I switch to my public IP instead of DDNS, I get the same issue.

Below is the config for wireguard

I'm using port 51821 and when I check to see if its open from port checker, it says its closed.
I have remote access LAN selected in the wireguard settings.

Any ideas on how I can troubleshoot this and get remote access to my LAN via wireguard? I had tried tailscale as well to see if something else was causing but that worked without issue, but I would rather use the Wireguard server on the router. Thank you in advance for your help!

I see you use in the peer section not the ddns one but a direct ip as endpoint.

Did you changed for testing?

please use the ddns one :+1:

If it fails with the ddns one, likely it is the dns being the culprit, you can try a manual dns of say 8.8.8.8 as global router dns option?

It only need to know once the domain to ip translation then you can switch back to the dns you like.

Please report the dns option you use currently, because it can be a bug issue.

You can't check WireGuard like this, you can only check by establishing a connection, not by any port testers.

2 Likes

The DNS issue seems to be resolved. I can now access the router from DDNS address and the public IP address. Now, when I connect to the wireguard server from my phone, using the config file generated by the Flint2, I am not able to use the internet on my phone. I am using DDNS in the config file now. I get DNS_PROBE_POSSIBLE and when I try to ping devices on my LAN when I am connected to wireguard on my phone, I can ping the router at 192.168.8.1, but my NAS at 192.168.8.100 and my desktop at 192.168.8.10, I get destination port unreachable. I'm getting a handshake from the client and server but its basically unusable.

These are my DNS settings

Than you again for your help!

It only lets me post 1 picture so I need to reply again to show a second

Why are your LAN devices in a different network than your router?
How does your network topology looks like?

Haha woops sorry. They are not on 192.168.1.xxx. That was a typo from memory of my old set up. They are all on 192.168.8.xxx

The router is hardwired directly to the PC and NAS.

Hello. Still having this issue. When It seems like the router is not resolving DNS requests properly. When I connect to the VPN nslookup, traceroute and pinging any DNS server does not work. I use termux on android to do all that I have tried google and cloudflare as the DNS on my router and in the wireguard config file and neither seem to work.

Put this profile on your Android phone and test if it works normally?

For the DNS on the profile, please fill in one IP, for example, only fill in 8.8.8.8