We ran into a strange connectivity issue this Friday.
We had a support tech out with a portable access point so we could get in a debug one of our locations.
I was able to get most of the devices online, but I was not able to get a random 2 or 3 out of the group. @CameronDiver was helping me out, but we couldn’t figure out the route cause.
Some of the devices would only be connected to the debugging tempory network, but could see the production network.
nmcli c up client_connection or
systemctl restart NetworkManager.service
brought that connection right back.
However later, I noticed I could ping some of the offline devices on IPs listed under them from when they were online. Using the hostvia tool, was I was able to ssh into two of them thru another device.
That revealed a strange status, everything but the vpn was working fine… I could ping 184.108.40.206, and other servers. I could even ping the what I think is a balena VPN server: 220.127.116.11 via the route:
18.104.22.168 dev resin-vpn scope link src 10.240.14.47 from
ip route s
I verified this with traceroute, it was a direct connection.
However, the device still showed up as offline.
Here are the OpenVPN logs.
I was able to get the device back online with:
systemctl status openvpn
I can do this from within my container, so my question other than why is this happening, how can I detect this happening and then reset the vpn from within the device. I know how to do the second part via the dbus, but my best guess for the first part is this endpoint but I can’t see to hit it when I am not in local mode.