NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

ctmutlow's avatar
Dec 19, 2017

FW 2.1.1.16 Update broken backhaul

The update from 2.1.1.12 to 2.1.1.16 has reduced backhaul status to POOR from GOOD; not what you like to see really

 

Sysyem configuration and positioning unchanged, tried both a reboot and resync still have a POOR Status on the backhaul.

 

System seems to work finein spite of this but link to satelitte slow to establish.

12 Replies

  • Update:

     

    Unticking the Enable Daisy-Chain Topology box (which had been enabled as default in earlier firmware) restored the link status to GOOD!

    • tagteam's avatar
      tagteam
      Virtuoso

      Honestly! Why do the latest firmware releases have that box checked by default? Sheesh!!

      • vascoigne's avatar
        vascoigne
        Aspirant

        Hi,

         

        Had exactly the same thing when updating the firmware to v 2.1.1.16.

         

        Do we need or not to enable the daisy chain connection?

         

        Don't like to have the satellite backhaul status to "poor"...

         

        Thanks

         

  • I have the same issue after my router updated to 2.1.1.16. Poor connection status on the satellite and it's connecting at 2.4Ghz instead of 5Ghz.

     

    So I logged into the satellite and noticed it still had to old firmware version installed on it.  So the "auto update" didn't seem to apply to the satellite. Looks like poor QA on this one.

     

     I manually updated the firmware on the satellite and it's now connecting properly at 5Ghz.  The only issue I still see is the satellite reports no connection back to the base but the base reports a good connection to the satellite.  I did see the blue connection light so I think it's working.

     

     

    • FredPhred's avatar
      FredPhred
      Aspirant

      After 30 minutes, my satellite now shows as connected at 5Ghz. So in my case updating the firmware on the satellite (and resynching them using the buttons on the back of each) resolved the issue. 

       

      I left the daily chaining on in case I decide to add another satellite to the system.

      • bukzin's avatar
        bukzin
        Aspirant

        I see some folks have firmware version 2.1.1.16

         

        My RBK53 (AKA RBR50) is showing version 2.0.0.74, same for my two satellites.

        Status states 'no new firmware version available'

         

        What changes to the backhaul were made?  How can I get latest version?