Sur un serveur Lime 1 à jour, sans anomalies dans les diagnostics, j’ai le message d’erreur suivant : ; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS
Ce message est apparu le 20/09 après un autre message Failed to resolve dyndns.yunohost.org et j’en ai bientôt 50 (!) qui arrivent parfois à raison de plusieurs en une heure.
Je ne sais pas ce que veut dire ce message, ni comment résoudre ce problème.
Merci pour votre aide !
What does mean : ; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS
I’ve got that message on a Lime 1 up to date server.
J’ai reçu le même message à raison de 5 fois par heure de 1 à 7h du matin, puis plus rien jusqu’à 17h23. Et là, 3 messages en 20 mn ! ; Communication with 2001:910:1410::1#53 failed: operation canceled update failed: FORMERR Could not update IP address to DynDNS
The Yunohost of one of my daughters loses IPv6 connectivity. I made a script (including some other stuff) that I run after boot, and when needed, to add a route for IPv6:
ip -6 route add default via fe80::2e3a:fdff:fe82:3f23 dev eth0
The global IPv6 gives no connection when added in a route.
Another problem I have with IPv6, is that there are 3 adresses:
Automatic (SLAAC?) adress, 2001:985::MAC scope global dynamic mngtmpaddr
The configured IPv6, 2001:985::…
Automatic local link, fe80::…
Yunohost diagnosis expects no. 2, but the SLAAC reappears on top every time and throws the diagnosis in disarray. Maybe it causes other problems as well.
I don’t have the error message since 2 days. I don’t know why.
ip -6 route gives :
::1 dev lo proto kernel metric 256 pref medium
2001:913:1fff:ffff::/64 dev tun0 proto kernel metric 256 pref medium
2000::/3 dev tun0 metric 1024 pref medium
fe80::42:acab dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev tun0 proto kernel metric 256 pref medium
fe80::/64 dev wlan0 proto kernel metric 256 pref medium
Finally, I have a better explanation: normally your ip should not change with this kind of VPN. But i suppose your VPN ipv6 switch between 2 values, cause your ISP push ipv6 through your vpn and give you a .cube with the ipv6 prefix fill too.
So i suggest you to empty the “ipv6 prefix” in the vpnadmin interface and save the change.