Forum Discussion

Ekkoh's avatar
Ekkoh
Tutor
Oct 22, 2026

RBRE960 and 169.254-address

I have 1 RBRE960 and 3 RBSE960 satellites. The RBRE960 is configured in AP mode, with a PR460X as the router. Two of the three satellites are connected to the RBRE via Cat6A Ethernet.

 

Sometimes several times a day, sometimes once a week, and sometimes only once a month, one or more of my RBSE960 satellites seem to "freeze" or lock up. When this happens, devices connected to the affected satellite are assigned a 169.254.x.x IP address.

 

To resolve the issue, I normally have to power-cycle the satellite. However, on some occasions, it starts working again on its own without a reboot.

 

When I check the Orbi app, it sometimes shows the RBSE960 as being connected via Wi-Fi even though it is physically connected via Ethernet. I have also seen the backhaul status reported as "Poor" several times, despite having a wired Ethernet connection between the RBSE960 and RBRE960.

 

I had a long-running support case with Netgear Support. After almost a year of troubleshooting, they eventually concluded that the hardware was faulty and replaced the entire system.

I received brand-new, identical replacement equipment, but unfortunately I immediately started experiencing exactly the same issue with the replacement units.

 

By that point, however, my Netgear warranty had expired, so Netgear is no longer willing to assist me with the issue.

 

Has anyone else experienced the same problem with the RBRE960/RBSE960, particularly when using wired backhaul in AP mode?

7 Replies

  • Link Local IP adresses are not assigned by the network.  They are created by each device when it is unable to get an IP address through the DHCP process:

    https://en.wikipedia.org/wiki/Link-local_address

    If the RBSE960 satellite is not responsive when devices attempt to renew their IP address using DHCP, then they will create their own "169" IP address.

     

    It would be really helpful to know how the PR460X and the Orbi units are connected.  Specifically:

    • The RBRE960 router WAN port is connected to the PR460X.
    • None of the RBRE960 LAN ports are connected to the PR460X.
    • The two RBSE960 satellites are connected to the Orbi router, not to the PR460X.
    • The third RBSE960 uses WiFi backhaul connection to the Orbi router.

     

    • Ekkoh's avatar
      Ekkoh
      Tutor

      The reason behind the PR460x is that I from the beginning thought that Orbi RBRE960 DHCP-server was the issue.

      But it didn't help with a new router.

       

      • The RBRE960 router WAN port is connected to the PR460X.
        • yes
        •  
      • None of the RBRE960 LAN ports are connected to the PR460X.
        • No satellites to PR460x
        •  
      • The two RBSE960 satellites are connected to the Orbi router, not to the PR460X.
        • Correct!
        •  
      • The third RBSE960 uses WiFi backhaul connection to the Orbi router.
        • Correct, often to one of the satellites.