Hello, I have a Flint router set up at home with the WireGuard server enabled. I’m encountering a peculiar issue where my Beryl travel router, equipped with the WireGuard client, is unable to access the internet from approximately 7:30 am to 3 pm EST. I attempted to ping the router’s DDNS host name, and it appears to timeout during this period. Any idea what might be causing this issue?
Without knowing more details like your ISP, VPN profile and other settings this might be just fishing in the dark.
So basically I would say the issue is that the internet does not work during these times. Now we have to investigate further.
1 Like
ISP: Bell Canada (Speed: 500 mbps up and down)
What’s the VPN profile and where to find it?
Here is the client config:
[Interface]
Address = 10.0.0.2/24
ListenPort = 25223
PrivateKey = mL…
DNS = 64.6.64.6
MTU = 1420
[Peer]
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = xxx.glddns.com:51820
PersistentKeepalive = 25
PublicKey = ay…
Is there maybe an forced reconnect by the ISP and the DDNS won’t update fast enough?
I’m not sure what you mean by “force reconnect.” As far as I can tell, the IPv4 hasn’t changed at all in the last few days.
Please change this to 1.1.1.1 or 8.8.8.8
Bell blocks 64.6.64.6 for some reason.
Maybe this is something that only exists in Germany 
When you use internet over landline (like ADSL) every night the connection will drop and you have to reconnect. It’s rare, but a guess.
But as you said the IPv4 hasn’t changed, this should be not an issue here.
I’m having the same issue after changing DNS to 1.1.1.1 or 8.8.8.8. Ping to DDNS host is timing out.
But this is not a DDNS issue.
DDNS will resolve the hostname to the last known public IP. If the public IP isn’t changing, we have no DDNS issue here.
To check ddns, please use a name resolve tool, like nslookup or dig.
nslookup [blank].glddns.com 8.8.8.8
should always point to [blank].8 in your screenshot. The 8.8.8.8 is the DNS server and optional for our test.
The fail in your screenshot is ping, not DDNS!
Now we have ruled this out, and going to ping.
Ping is sending an ICMP package. ICMP is good to test if a host is available. But when it comes to the internet, many people have the opinion ICMP is the pure evil, every hacker in the world can hack you, just by ping your host … So they engineered the ‘stealth mode’.
I’ve seen ICMP blocks from LAN to WAN in corporate networks … It exists, believe me.
You are saying you are using a travel router. So I assume you are traveling and switching networks.
I suggest to use iperf3 as solution in this case: iPerf3 for beginners
Of course every other TCP or UDP service will work as well, but please don’t open a http server on your router, exposed to the internet! there are bad people out there, which know the banner of embedded http services and what to do with it.
Install the iperf3 client on your client computer. And I’ll say this will work, even if the WG does not. Maybe because between 7:30am and 3pm anything in your remote LAN is blocking WG.
1 Like
Seems that the issue is that your IP is changed and the ddns is not updated. Can you confirm?
You can find out your public IP and the IP the ddns is resolved to, then do a coparison.
But pls do change the ddns. Bell is blocking 64.6.64.6 which may cause a lot of issues for you later.
I have double checked my public IP and it hasn’t changed at all.