[Bug] Tunnel settings are not refreshed when renaming a node

[VA2XJM]

While doing network maintenance jobs, I needed to rename a distant tunnel client node to reflect a site callsign change. The node name has been also changed on the tunnel server side. Both from the GUI.

After the client node has been rebooted, the tunnel will not go up. On both side, we can see the connection is rejected.

I logged in into the client node, edited /etc/config/vtun and /etc/config.mesh/vtun to change the callsign portion of the "name". Rebooted the client and now the tunnel will go up.

---

Changes needed: When the node name is changed, the tunnel "name" values for tunnel clients must also be changed. Those values could be computed at every reboot to make it simple.

[k1ky]

Ditto - I have experienced this issue for over 6 years. I just reported it on the kg6wxc MeshLink as well. Changing the name back on the tunnel server side seems to restore the connection. Thanks for digging into this. I look forward to a fix as I need to rename more tunnel client nodes.

[k1ky]

It appears that something that I have done - disabling/reenabling server side connection, rebooting server and client nodes - the connection now works under the new name. I checked the /etc/config files listed above on the client node and the new name appears to be correct in those files. I had not edited these files, so "something" magically corrected the situation after many hours. IperfSpeed 0.6 was also installed.

[ab7pa]

@k1ky Tom, from what I see in the code, every time you click Save Changes on the Tunnel Client page all of the config settings are written to those config files and both oldrd & vtund are restarted. There is no field in the UI to enter the nodename, but under the covers the nodename is pulled from the current name on the node. So if you change the nodename of a tunnel client then you should also go to the Tunnel Client page and click Save Changes (even though it looks like you're not making any changes). That might provide a workaround for you. Let me know if that works. In the meantime we'll see if there is a way for that "magic" to happen directly from the Setup page when you change the nodename on a tunnel client. On the tunnel server side there is a field for the Client nodename, so that should be changed and then click Save Changes on the Tunnel Server page.

[k1ky]

Yes, I did a save in the Tunnel Client section after renaming the Client node and that updated the config file. Good work-around for now.

[VA2XJM]

@ab7pa Thanks for that finding. :)