NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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)
- 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?
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.
bryan3301 wrote:
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?That is a perfectly acceptable solution and the RBR960 (like the RBR50 before it) should have no problem with it*. The trace routes show the laptop going through the router to the Proxmox host and then to the virtual server on the Proxmox.
Is it correct to assume that the router has a static route defining 172.20.73.11 as the gateway to 172.216.77.x?
* There was a post several months ago where the user wanted to VPN into two different Orbi systems and was frustrated that the both Orbi's defined their VPN subnets the same and could not be configured. As long as the target VPN networks are different from 172.xxxx and each other, this is a fine solution.
Intermittent issues are the very devil to diagnose. It is natural to assume that "What changed?" was the router transition. It would be an enormous chore to swap back to the RBR50 system to validate that the problem (a) never occurs with the RBR50, and (b) can be reproduced at will with the RBR960.
CrimpOn Thank you for the continued feedback; this one is a head scratcher for me as I feel it should work. After all, it worked on my old RBR50. Routing and configuration were all set the same (with the exception of the IP address change, SSID/password change, and, the RBR960 has two extra WiFi networks, one for IoT and one for dedicated 6E).
Does the metric value on the route on the Orbi matter? I have tried with 2, 3, 10, 12, 15 and it does not seem to make a difference (not that I thought it would).
I have Tailscale configured on a couple hosts on this network as my VPN. I have no problems staying connecting to the servers when on VPN and they have no problems staying connected to the outside world. I only seem to have the issue when using my laptop at home on the WiFi network (I haven't tried physically connecting my laptop via Ethernet yet). This leads me to think it is bug with static routing on Orbi.
ORBI STATIC ROUTE CONFIGURATION
Route 1
Name: lab1.local
Private: Checked (I also tried /w unchecked)
Active: Checked
Destination IP Address: 172.16.77.0Subnet Mask: 255.255.255.0
Gateway IP Address: 172.20.73.11
Metric:10
Route 2
Name: lab2.local
Private: Checked (I also tried /w unchecked)
Active: Checked
Destination IP Address: 192.168.77.0
Subnet Mask: 255.255.255.0
Gateway IP Address: 172.20.73.12
Metric:10172.20.73.11/24 (172.16.77.0/24) and 172.20.73.12/24 (192.168.77.0/24) are the Proxmox hosts. In parenthesis is the vSwitch network for each.
