Yesterday, Rick, k7fyi, and I assisted another ham in upgrading one of his Rockets to the new AC version. About an hour after the upgrade, the ham made a minor change to the name of his node, changing 'NE' to 'ENE'. Not long after that, Rick and I could no longer connect with any of OUR respective nodes via dtd. Only after rebooting everything could a link be reestablished with our respective nodes.
My eight radios all run 4.26.1.0, Ricks 7 radios run a combination of 4.26.1.0 and 3.25.10.0.
Looking back, this isn't the first time this has happened to us since version 4.26.1.0 was released and after a node name was changed by someone on the Las Vegas network.
Anyone else experience this? I can see the node making the name change might have an issue, but two remote nodes? Both experiencing the same problem?
thanks...
Richard ko0ooo
My eight radios all run 4.26.1.0, Ricks 7 radios run a combination of 4.26.1.0 and 3.25.10.0.
Looking back, this isn't the first time this has happened to us since version 4.26.1.0 was released and after a node name was changed by someone on the Las Vegas network.
Anyone else experience this? I can see the node making the name change might have an issue, but two remote nodes? Both experiencing the same problem?
thanks...
Richard ko0ooo
I've noticed that the devices can route fine if you know the new name and type manually. What doesn't update quickly is the navigation information that shows up in the "See what is on the local mesh" function. Rebooting the unchanged node will force a restoration of that lookup information so your comment makes sense to me.
Ed
Richard