Upgrading a NSM2 from 3.15.1.0 to 3.16.1.0b01.
1) I tried to load the "Allow OTA upgrade over slower links" package, but it errored and failed to load.
2) Made the OTA changes by hand through the terminal
3) Uploaded the beta but forgot to set the "Keep Settings" option.
When the node came back up it was in in a transparent AP (bridge) mode with the node name "mesh node" and apparently no IP address. I.e. it did not get a dhcp lease from a co-located (dtdlinked) node and was not on 192.168.1.1. I tried several resets and finally a power-on reset caused the node to come up on 3.16.1.0b01 in NO-CALL mode and I was able to finish the configuration.
A question/suggestion. In AP mode(s) could the node still request an IP address so it could still be accessed via the GUI.
Richard - wb6tae
1) I tried to load the "Allow OTA upgrade over slower links" package, but it errored and failed to load.
2) Made the OTA changes by hand through the terminal
3) Uploaded the beta but forgot to set the "Keep Settings" option.
When the node came back up it was in in a transparent AP (bridge) mode with the node name "mesh node" and apparently no IP address. I.e. it did not get a dhcp lease from a co-located (dtdlinked) node and was not on 192.168.1.1. I tried several resets and finally a power-on reset caused the node to come up on 3.16.1.0b01 in NO-CALL mode and I was able to finish the configuration.
A question/suggestion. In AP mode(s) could the node still request an IP address so it could still be accessed via the GUI.
Richard - wb6tae
Are you sure that you are keeping it CHECKED?
I did an OTA sys upgrade to an M2 with today's 16-beta and it did not come back (many minutes).
After a push-and-hold-the-button reset, it showed up on 192.168.1.1 but not accepting connections or showing ports.
After another reset it came up like a new one - with no call. First try to enter and save a call did not work. Back to 192.168.1.1 no-call.
The second time I entered the call and saved, it started up the DHCP server and began to work. No settings were kept.
So that was not much fun :-(
Where you upgrading from 3.15.1.0? or a beta?
This was from the "original" 3.16.1.0b01 to the most recent version - hoping to pick up the change in the way the firewall works for the tunnel node.
After flashing the firmware OTA - and failing - the behavior of the LED's vs reset button was not normal at all. Normally I expect to see something at about 7 seconds. That did not happen, so I ended up holding the button a bit longer.
I guess this would be an opportunity to mention that I think it would be nice if revisions to the beta had a "build number" or some easy way to distinguish between them. I think that is quite usual in other places where experimental/beta versions are issued, no?
Ok so it was kind of a pointless exercise then - except I think I read someone else did an (OTA) upgrade that failed in quite a similar way.
I think all my other firmware flashing was direct connect from the PC to the wireless router ...