VPN client on Slate AX not connecting to Puli Wireguard server

Technical Support for Routers VPN, DNS, Leaks
1

I just helped someone setup a VPN server on their Flint (10.0.0.1 server IP, 51820 port), and now helped them create 2nd backup Wireguard server on the same network (10.1.0.1 server IP, 51821 port) on their Puli. They have the Puli receiving internet from ethernet on the same network as the Flint, but then failover to the cell modem.

I tried creating client profiles with and without DDNS and neither works. I saw a similar thread with the same log error and so I updated the Puli to firmware v4.3.17 with no luck. https://forum.gl-inet.com/t/slate-ax-gl-axt1800-wireguard-issue-rekey-timeout/

TThu Jul 25 23:41:17 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Thu Jul 25 23:41:52 2024 daemon.notice netifd: Interface 'wgclient' is now down
Thu Jul 25 23:41:52 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Mon Jul 29 21:40:27 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Jul 29 21:41:31 2024 daemon.notice netifd: Interface 'wgclient' is now down
Mon Jul 29 21:41:31 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Mon Jul 29 21:43:00 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Jul 29 21:43:00 2024 daemon.notice netifd: Network device 'wgclient' link is up
Mon Jul 29 21:43:00 2024 daemon.notice netifd: Interface 'wgclient' is now up
Mon Jul 29 21:43:00 2024 user.notice wgclient-up: env value:T_J_V_ifname=string J_V_address_external=1 USER=root ifname=wgclient ACTION=KEYPAIR-CREATED N_J_V_address_external=address-external SHLVL=3 J_V_keep=1 HOME=/
 HOTPLUG_TYPE=wireguard T_J_V_interface=string J_V_ifname=wgclient T_J_V_link_up=boolean LOGNAME=root DEVICENAME= T_J_V_action=int TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin CONFIG_LIST_STATE= J_V_interface=wgclient K_J_V= action ifname link_up address_external keep interface J_V_link_up=1 J_V_action=0 T_J_V_address_external=boolean N_J_V_link_up=link-up T_J_V_keep=boolean PWD=/ JSON_CUR=J_V CONFIG_SECTIONS=global AzireVPN Mullvad FromApp group_1061 group_4028 group_6995 group_9784 peer_2232 peer_2002 CONFIG_cfg030f15_ports=
Mon Jul 29 21:43:00 2024 user.notice firewall: Reloading firewall due to ifup of wgclient (wgclient)
Mon Jul 29 21:43:16 2024 daemon.notice netifd: Network device 'wgclient' link is down
Mon Jul 29 21:43:16 2024 user.notice firewall:
Reloading firewall due to ifdown of wgclient ()
Mon Jul 29 21:43:16 2024 daemon.notice netifd: Interface 'wgclient' is now down
Mon Jul 29 21:43:34 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Jul 29 21:44:01 2024 daemon.notice netifd: Interface 'wgclient' is now down
Mon Jul 29 21:44:01 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Mon Jul 29 21:46:39 2024 daemon.notice netifd: Interface 'wgclient' is setting up now

The Wireguard server on the Puli has the green indicator light. The Slate AX's VPN config file I tried setting DNS = 10.1.0.1 and also 1.1.1.1 without success.

There are no conflicting subnets: Flint (192.168.10.1), Puli (192.168.6.1), Slate AX (192.168.8.1).

2

There are conflicting subnets I would say - the guest networks. You need to change them as well.

3

Hm... did you see the last sentence though? I changed the LAN IPs so none of them match. And the internet source to the Slate AX is an iPhone hotspot by the way.

I'm verifying the LAN IP of the ISP home router though. I can't remember, maybe that's the issue.

4

I wonder if the empty ListeningPort for the Puli client config is defaulting to 51820 which is the problem since it should be 51821.

5

Pls post the port forward settings on the main router.

6

Yeah, I think we found the issue. The Puli was plugged into some access point switch (managed) with its own DHCP server, so the IP got changed and obviously wasn't matching the port forwarding settings.