I have 2 beryl setup. One running wireguard server connected to my cox router. i have port forwarding rules setup on router.
The second beryl is connected to router wifi. I am trying to run wireguard client on it and it never starts. Here is the log :
Sun Sep 29 18:09:25 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 1.00 seconds...
Sun Sep 29 18:09:30 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 1.20 seconds...
Sun Sep 29 18:09:36 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 1.44 seconds...
Sun Sep 29 18:09:43 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 1.73 seconds...
Sun Sep 29 18:09:49 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 2.07 seconds...
Sun Sep 29 18:09:56 2024 daemon.notice netifd: wgclient (3386): Try again: `redacted.glddns.com:51820'. Trying again in 2.49 seconds...
Mon Sep 30 09:59:19 2024 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Sep 30 09:59:20 2024 daemon.notice netifd: Interface 'wgclient' is now down
Mon Sep 30 09:59:20 2024 daemon.notice netifd: Interface 'wgclient' is setting up now
Mon Sep 30 09:59:20 2024 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Mostly it could be an issue that both network segments are the same (so both 192.168.8.x) for example. But please have a look into this guide How to troubleshoot WireGuard to check all stuff that might be the issue here.
If it is like this (please check before!) you will need to change the LAN network range by changing the IP of the router from 192.168.8.1 to something different like 192.168.18.1 for example.