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

Forum Discussion

bryan3301's avatar
Nov 08, 2023
Solved

RBRE960 - Intermittent Connectivity Issues

I have two (2) Proxmox hosts. Each host is connected to my network (172.20.73.0) via a wireless NIC (I tried wired and had the same problem) and I am using NAT and MASQUERADE. On each Proxmox host, I have a vSwitch; one host as 172.16.77.0 and the other host as 192.168.77.0. This has been working fine for months on my old Orbi Mesh system (RBR50).

Since upgrading to the RBRE960, I have noticed connections to containers and VMs fail. I can be in via SSH or RDP for hours while at other times, the connection freezes after seconds or minutes. Most times I can reconnect immediately, while other times, I must wait minutes or hours, or, reboot the Proxmox host. I am connecting from my laptop which is connected to WiFi.

The containers and virtual machines can communicate with one another, as well as, externally to my 172.20.73.0 network and the Internet.

I included a trace route from my laptop at the end of this message.

I am puzzled and looking for ideas and suggestions on how to address this. Your help and feedback is much appreciated. Thank you!!

Code:
PS C:\Users\admin> tracert 172.16.77.2

Tracing route to 172.16.77.2 over a maximum of 30 hops

  1     3 ms     3 ms     4 ms  router.lab.local [172.20.73.1]
  2     9 ms     5 ms     7 ms  proxmox1.lab.local [172.20.73.11]
  3   248 ms   215 ms   432 ms  172.16.77.2

Trace complete.
PS C:\Users\admin> tracert 172.16.77.25

Tracing route to 172.16.77.25 over a maximum of 30 hops

  1     5 ms     4 ms     3 ms  router.lab.local [172.20.73.1]
  2    46 ms     6 ms    23 ms  proxmox1.lab.local [172.20.73.11]
  3    63 ms     8 ms     6 ms  172.16.77.25

Trace complete.
PS C:\Users\admin> tracert 172.16.77.25

Tracing route to 172.16.77.25 over a maximum of 30 hops

  1     5 ms     3 ms     3 ms  router.lab.local [172.20.73.1]
  2   218 ms    23 ms     8 ms  proxmox1.lab.local [172.20.73.11]
  3   459 ms     8 ms    67 ms  172.16.77.25

Trace complete.
PS C:\Users\admin> tracert 172.16.77.2
  • If I understood support correctly, they are having a known issue with the RDP protocol on the RBRE series. Engineering is working on a fix; however, the agent was not sure of the ETA. The best guess is Q1 of 2024.

     

    I am going to return this system and stick with the ASUS ZenWiFi Pro XT12. It has worked flawlessly, is much more feature rich (much better software), and, about half the price of the Orbi system.

     

    I will say I do appreciate Netgear products and cannot speak negative about the company. I had great success with my RBR50 system, as well as, many other Netgear products over the years. Support and engineering from Netgear on this issue was quite good. I didn't spend much time in lower levels nor did I have to repeat my story repeatedly. The team worked very collaboratively with me and were always extremely polite and calm.

32 Replies

  • CrimpOn's avatar
    CrimpOn
    Guru - Experienced User

    Is it correct to assume that the LAN setup for the RBR960 is exactly the same as the RBR50 LAN setup?

     

    It is a bit unusual to see an Orbi router with the LAN IP subnet defined as 172.(anything)

    • bryan3301's avatar
      bryan3301
      Tutor
      I did change from a 192.168.1.0 network to 172.20.73.0 network to avoid conflicting with more common networks (for when I VPN). Does Orbi get confused with 172 networks?
      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User

        192.168 shouldn't be conflicting with any VPN networks. VPN should auto avoid and configure networking that's not on same subnet as 192.168.1.x. You can also try using 192.168.0.1 as well. What I use. 

         

        I'd try the default subnet setting on the 960 to see if it works if you had been using that before on your prior Orbi system. 

         

        172 should work as well as it's a private subnet for home use.