The 2.1.2.18 nightmare

I work out of town during the week, so when I came home this past weekend and saw there was a firmware update pending, I hit these boards to get a feel for how it was working. As there appeared to be much difficulty around the 2.1.2.18 firmware, I decided to look  for a way to keep the update from happening automatically and came across this thread.   Having familiarity with Telnet sessions and Putty, I followed the steps as outlined by the OP. I logged out and logged in to check the settings. I also found the ability to log in to the router while away from home.  Note also that one of my two satellites was unable to download the firmware update, which I thought would have also prevented the auto-update from happening.  Like many of us, I didn’t want a toasted network with me being away from home for the week. There would have been chaos. 

I left for work, and from the hotel this morning I wanted to test out the remote access feature. Lo and behold I was able to attach the router from the hotel, and then noted that my firmware had been upgraded.  Fortunately, the network appears to be running as I immediately connected to my TiVos remotely (hardwired via MoCA). I had wifey confirm by checking her laptop (wifi). I’m also happy to report that my wireless settings appear to of been preserved i.e. my custom SSIDs and passwords. 

 I did see two things of note however. First, the satellite that was unable to download the firmware is still listed as on the old 2.0.0.34 Software. This satellite is furthest from the router and when I come home this weekend I’ll move it closer and attempt update it. Or if everything is working, maybe I won’t :-). Also, on the interface the satellite that was updated shows the backhaul connection as poor. I wonder if there is a way to address this.

I guess im one of the lucky ones.