Velica: Symptoms of aging?

[okram]

I have a pair of Velica that run in mesh mode. Both were bought together in February 2022 and have been running always-on since then. Recently, I’ve experienced some latency or dropped connections, in particular, when DNS resolving. For example:

    ~  dig telemundo.com                                                                                                   ✔ 
;; communications error to 192.168.8.1#53: connection refused
;; communications error to 192.168.8.1#53: connection refused
;; communications error to 192.168.8.1#53: connection refused

; <<>> DiG 9.20.11 <<>> telemundo.com
;; global options: +cmd
;; no servers could be reached

I get maybe 10-20 good DNS requests/answers and then for a few seconds connection will be refused.

I’ve configured the router with manual DNS resolvers to see whether it might have something to do with my ISPs resolver, but that didn’t make a difference. Also, the cable modem was just replaced. It has its own Wi-Fi and when I connect to it, I no longer get this kind of behavior. So, I’m wondering if this might have to do with the router aging…?

[bruce]

Hello,

Seems it shouldn't be aging.

You can check on your PC (Win, CMD) to check if there are any packet loss:

ping dns.google -t
ping 8.8.8.8 -t 

[okram]

After going through various steps, I think I might have found the problem.

There was a Wireguard config stored on the router twice once without a name and the same with a name. While I did not check the format of the underlying config file, I suspect that this was the reason that the Wireguard client was not connecting. At the same time there was a VPN policy to use the VPN for the guest network. Maybe this in some way caused the router to constantly reconfigure its networking and maybe that led to the problems I was experiencing. I’m aware that this is quite vague, but I have since reconfigured the router and cannot reproduce the fault anymore. I’m just sharing this here in case someone faces a similar situation.