>From these mesh nodes, are you able to: ping 8.8.8.8 successfully? resolve DNS records successfully? Eg: nslookup google.it
The cURL exit code 60 (or CURLE_PEER_FAILED_VERIFICATION) indicates an SSL certificate problem, meaning cURL cannot verify the legitimacy of the server's SSL certificate. Do all your devices suffer from the same or only these mesh nodes? F. On Sun, 1 Feb 2026 at 22:29, Michele Salerno <[email protected]> wrote: > Hi, > > My network is: > > LAN network is 10.27.0.0/16 > Backbone network is 172.27.0./16 > VPN network is 172.27.253.0/24 > Mesh network is with AutoIP ( > https://openwrt.org/packages/pkgdata/avahi-autoipd) > > The routers connected via cable are fine, but a router connected only to > the mesh network does not communicate with openwisp-monitoring (routing is > ok but not with monitoring). > > I tried to add the interface in the /etc/config/openwisp file, but I get > this error: > > daemon.err openwisp: Failed to connect to controller while getting checksum: > curl exit code 60 > > > ROUTER: > > # ip r > default via 169.254.9.97 dev br-mesh proto bird metric 50 > default dev br-mesh scope link metric 1007 10.27.0.0/24 via 169.254.9.97 dev > br-mesh proto bird metric 50 10.27.10.0/24 via 169.254.9.97 dev br-mesh proto > bird metric 50 10.27.22.0/24 via 169.254.9.97 dev br-mesh proto bird metric > 50 10.27.25.0/24 dev br-lan proto kernel scope link src 10.27.25.1 > 169.254.0.0/16 dev br-mesh proto kernel scope link src 169.254.7.9 > > OpenWISP > > # ip r > default via 10.27.22.5 dev ens19 onlink 10.27.0.0/24 via 172.27.253.2 dev > zt6qwgqjee proto bird metric 50 10.27.10.0/24 via 172.27.253.5 dev zt6qwgqjee > proto bird metric 50 10.27.22.0/24 dev ens19 proto kernel scope link src > 10.27.22.252 10.27.22.0/24 dev ens18 proto kernel scope link src 10.27.22.15 > 10.27.22.0/24 via 10.27.22.253 dev ens18 proto bird metric 50 10.27.25.0/24 > via 10.27.22.253 dev ens18 proto bird metric 50 172.27.253.0/24 dev > zt6qwgqjee proto kernel scope link src 172.27.253.1 > > OpenWisp does not recognize the 169.254.0.0/16 network. > This is most likely the problem. > > Is it possible to use subnet rules to assign an IP address for the mesh > interface so that you don't have to manually intervene on each router? > > If “yes,” how can I do it? > > Best regards, > > Michele > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion, visit > https://groups.google.com/d/msgid/openwisp/819da8ee-24f3-482a-b0d7-e1c739eabe2e%40gmail.com > <https://groups.google.com/d/msgid/openwisp/819da8ee-24f3-482a-b0d7-e1c739eabe2e%40gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6Kae4_hKdW%2BTgayodFOJbYPwCKdV_kQ%3D%2Br-YNuFNNWSGg%40mail.gmail.com.
