Flint 3 v4.9.0: Client Devices Unable to Connect to the WireGuard Server

Router
1

What am I missing with WireGuard Server flint 3 4.9 firmware. I have configured the WireGuard Server with the default settings and started it. I have created several Profiles and none of them can connect to the Flint 3 WireGuard server….

I have created WireGuard Server and client on other non-Gl.iNet routers the same way and they work fine….. What on earth am I missing?

Thanks.

How to route all traffic from wireguard server to wireguard client?
2

Hi

Did you set up the WireGuard Server by following the guide below?

If so, you may find the following troubleshooting guide helpful:

In most cases, it is important to verify the following:

  1. Whether your home network has a public IP address.
  2. Whether the public IP is assigned directly to the Flint 3, or if the required port forwarding has been configured correctly on the main router.
1 Like
4

Sure Did! With the exception I do not use a travel router so anything after that was useless for me.

  • I have an FTTP connection to the internet which is directly connected to the Flint.
  • I have enabled DDNS - the address xxxx.glddns.com:51280 does work to access the Flint from a browser.
  • WG config file is using the xxxx.glddns.com:51280 for the end point.
  • I find that the "what's MY IP Address" is different to what the Flint shows "Ethernet1 WAN port" show.

I have now resolved the issue by changing the "Endpoint" entry in the WG configuration file to that shown as the "Ethernet1 WAN port" of the Flint "Internet" web page. That then worked and WG is working and the Flint "WireGuard Server" web page show the client and the connection status.

So to summarise - I had to change the "Endpoint" entry in the WG Config file to that shown on the "Internet/ Ethernet1 WAN" file and not use what the WG Config had.

But it gets even more complicated - all that did not work on my recent model Samsung phone - I had to use the IPv6 for the endpoint - the IPv4 nor did the GLDDNS work....

Beats me. :roll_eyes:

OK now that I have some idea of where the problem is I can reset the firmware to default and start again - wish me luck - it sure has been a tedious process.

I have configured and used WG on other brand routers that have worked without issues right out of the box, so to speak.

EDIT /Update.........
Well that did not work! I tried it for real out in the real world..... I am connected to the mobile data network on my mobile phone and BT tethering to the phone from my Samsung TAB8 at the local coffee shop just up the road. So back to square one. It did work at home on the WiFi network. I have not yet reset the firmware.

5

A further update.

After many hours and frustration I may have found the cause of my issues. I do not think that the Flint 3 WireGuard Server (WG) or just WG does not work well with my RSP CGNAT. I have opted out of CGNAT and things seem to be better, with a few quirks. (It may be different tomorrow....lol)

  • I have to set the end point in WG to the WAN (v4) IP address - I have not tried the WAN v6 address.
  • WG does not connect / work if I use the glddns - there is an exception to this - it gets weird!
  • xxxxxxglddns.com only resolves if my desktop PC is on the same network 192.168.8.xxx - It does not resolve if I am not on the same network.
  • With CGNAT disabled, the result from "What's My IP Address" shows the same WAN IP addresses as the WAN port on the Flint. This used not to be the case - I would get different IPs from "What's MY IP Address" to that shown in the Flint WAN port.

My use case for WG is to connect my Samsung TAB 8 - it does not have mobile data capability only WiFi - back to my home network. I do this by BT tethering the TAB to my mobile phone which is using the mobile data. I then enable WG on the TAB and all now works. This scenario seems to be working but I have yet to try it when away from home at the local coffee shop.

xxxx.glddns.com seems to work when I punch that URL into to the browser on the TAB on whichever network it is connected to, whereas the desktop has to be on the same Flint network - go figure.

My mobile phone connects to WG both when on mobile data or WiFi.

So to summarise -

  • WG server / Flint3 does not like an internet connection using CGNAT so it seems.
  • xxxxxglddns.com is picky on which network it works on.
  • I cannot use xxxxxglddns.com as an endpoint in the WG config file
  • WG works when I select the WAN IP address as the endpoint.
6

OK, sorted this out..... Long story short I had an AdGuard filter blocking this address on the network I was connecting to - all good now.

I have opted out of CGNAT with my RSP and now DDNS works too - so all in all things Aare looking great and I have learnt a lot about the FLINT 3 - Just waiting for the Flint 4.

1 Like