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

Forum Discussion

Mstrbig's avatar
Mstrbig
Master
Dec 12, 2020

RBR750 and RBS750 new firmware V3.2.16.22_1.4.9

A new firmware V3.2.16.22_1.4.9 push for the RBR750 router and RBS750 satellite came out today. Since I always install the latest firmware when it comes out, I updated my RBK753S system. The update ...
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Dec 13, 2020

You can upgrade to test your own loop back configuration. If it's not fixed, then downgrade. Check the RBRs web page to see if the new version is available there.

 

orbira wrote:
I am also one of those who upgrade immediately. But this time I haven’t done that because of two reasons.

1. On the support site for RBK753 I don’t see the new version yet even though orbi app says there is a newer version available.
2. The port forwarding is broken on the 3.2.16.6 due to nat-loopback and Netgear had given me a firmware with hot-fix for that. Need to confirm that the issue is fixed on this version before I upgrade.

Can someone who has upgraded confirm the 2nd one please.

Thanks

 

larryindublin's avatar
larryindublin
Luminary
Dec 13, 2020

Wouldn't the typical way of releasing a hotfix version assume that the fix rolls foward into new (and higher numbered) versions?

  • orbira's avatar
    orbira
    Apprentice
    Dec 13, 2020
    larryindublin wrote:

    Wouldn't the typical way of releasing a hotfix version assume that the fix rolls foward into new (and higher numbered) versions?

    I would hope so, but given the file (/proc/sys/net/bridge/bridge-nf-call-iptables) is empty (info provided by Mstrbig, unless it is fixed some other way, I don't see same patch applied. 

     

    Thanks

    • Mstrbig's avatar
      Mstrbig
      Master
      Dec 13, 2020
      orbira wrote:
      larryindublin wrote:

      Wouldn't the typical way of releasing a hotfix version assume that the fix rolls foward into new (and higher numbered) versions?

      I would hope so, but given the file (/proc/sys/net/bridge/bridge-nf-call-iptables) is empty (info provided by Mstrbig, unless it is fixed some other way, I don't see same patch applied. 

       

      Thanks

      The patch was possibly created for those experiencing the issue you have, and others that don't have the issue would not need it. That same patched firmware was given to me to solve an IPv6 issue, but it didn't work, so I reflashed 3.2.16.6.

      I've never experienced the NAT issue posted. I'm thinking, certain configurations mixed with certain devices and Internet Service Providers, and even possible Regions, could possibly play a role in some users experiencing certain issues while others don't.

      And as an example the issue reported, with IPv6, that I and others experienced, was not experienced by FURRYe38. He stated he has never experienced it.

      • orbira's avatar
        orbira
        Apprentice
        Dec 13, 2020
        FWIW, upgraded the firmware and the port forwarding continues to work. So all good here. Glad I am off the custom hot fix to main stream firmware.

        Thanks