NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Where is traffic separation for the Guest network?
Set up the AX 6000 to replace a 4 unit Orbi Pro system with only minor hiccups. One of the main reasons I used the pro was the ability, VS the regular orbi at the time, to separate the three networks. My Tesla could not connect on the regular Orbi system despite 9 months of trouble shooting. Before buying the AX, I confirmed in the manual that you could separate the guest and main networks, but after installation and update to the latest firmware (3.2.8), there is no option to separate. Not in the Guest Network section nor anywhere else. Everything else is great. 2 units have faster speeds and way better coverage than the 4. But I need the traffic separation to keep the Tesla connected. Any thoughts?
16 Replies
I'm not sure I can be any help, but would like to understand your problem a bit better anyway.
When you say your Tesla, do you mean an automobile or do you have one of their power systems?
Next, what do you mean by traffic separation? Are you connecting your Tesla to the guest network? If, so why? It can't be part of your primary network? That seems very odd.
If by traffic separation, you mean that it requires a different IP address range from the main network, I read here where someone was able to telnet into the RBR850 and change the guest network address scheme following the instructions for the RBR50, so that might be an option for you.
It IS strange. Netgear has never been able to get this fixed, and Tesla (on the car side) has no clue, but the prevailing theory online is that Tesla's circa 2015 wifi chip doesn't play nice with DLNA devices on the same network. And I have many, and so you would think the Guest network would be a solution. But in the normal Orbi setup, despite the different logins, network traffic on the main can see the network traffic on the guest and so no go. On the Telsa, you see it briefly connect, and then the whole wifi reboots in an endless connect/reboot cycle. The Orbi pro solved this dilemna by allowing you to choose whether the employee and guest networks can see the main network, or whether they each get individual access to the internet but not access to the other networks (network isolation), or whether they can all see each other (which would, for example, be helpful in allowing folks on the guest network to access network printers). Prior to the pro I had to have a separate ap on a subnet. The manual for the AX Orbi says you have the choice whether to allow network isolation in the same way as the pro, but there is no actual option in the firmware. So I'm re-hosed!
I don't have this new model, but it's possible to do what you want with older model RBR50 via Guest Network. By default Guest Nework is not allowed to see local network and other clients on the same Guest network. If you put Tesla on Guest with a separate Guest SSID, it should be isolated from the rest.
Check out this: How to separate 2.4GHz/5GHz SSIDs for Guest Network
