NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Odd Issues with Orbi Pro WiFi 6 System
I setup my new WiFi6 Orbi Pro system at home (AX6000 - 1 Router + 2 satellites) a couple days ago and have encountered a few odd issues since that I'll outline here. All devices are at what I believe is the current firmware (V3.1.1.102).
The first issue I encountered is that although I had a number of my devices connected to a SSID (setup as guest SSID on old Orbi WiFi 5 systems and as WiFi network 3 (IOT) on my Pro System with same name/key), the IP's assigned to those devices came from the default (1) range vs IOT (30) as I expected. I went into the GUI to check and for some reason, the VLAN Profile for Wireless 3 was set to Default(1). That seemed easy enough to fix so went ahead and changed the VLAN profile to IOT (30). While I then saw some of the IOT devices getting assigned a 192.168.30.X IP, I then came across the 2nd issue.
For some reason, both the web GUI and Insight app are showing these devices as connected to the Employee SSID which I currently do NOT have enabled. This seems like some sort of bug but honestly not sure what to make of this. Has anyone seen this behavior? Of all the issues, this is one I would definitely like to get figured out.
The third issue I'm seeing is a particularly odd one. When I look at the MAC addresses for some of my Ring devices (specifically Chime Pro), the MAC address that the web GUI and Insight app are displaying is off by 1 character (specifically last character in last octet) from what Ring's own app is showing and what is displayed on the device itself. For instance, the MAC address shown by the Ring app and displayed on one of the Chime Pro's ends in 8D but Orbi/Insight is showing 8E. Everything up to that last character is identical. I have several of the Chime Pros and see similar behavior with all but one where the MAC address matches on both sides. Not sure what to make of this one either, particularly with the one outlier that I have.
If there's any additional information I can provide, let me know.
Thanks!
Bill
2 Replies
Hi wesmithjr100
Wish you a very happy new Year 2021. Thank you reaching NETGEAR community.
Issue 1 - Are you saying IP address are getting assigned from Default VLAN even though you have configured (30)? Are you seeing this issue only when IoT device connected to Satellite? ( we have some known issue here when device connected satellite, Fix will be available in our next version)
Or did I mis understood your question? Please help me to clarify.
Issue 2 - Send us the debug logs from local web UI by accessing https://<ip address of Orbi 6>/debug.htm -> Click on start capture -> Save debug log. Also send us the diagnostic logs from Insight to compare.
Issue 3 - Again we need logs. Send us the screen capture ( Ring's app, Insight and Orbi's local UI).
Please upload all the debug logs files and screen captures onto google drive or something similar. Send me link via PM.
We will check and update.
Have a good day!
Raghu
RaghuHR Raghu,
Thanks for the reply! See my feedback below for reach of the issues I had noted
Issue 1 - In re-reading things there, I can see I wasn't as clear as I probably could have been. Before replying, I took another look and things are even stranger here than what I initially noted. Starting from the beginning and in a little more detail - On my old Orbi 5 environment (Home / NOT Pro), I had 2 SSIDs setup - one that all my devices minus my IOT stuff connected to and then the Guest SSID, which I primarily used for IOT devices. When I setup things with Orbi Pro, I initially only had Wireless 1 enabled and then later enabled Wireless 3 (IOT) using the same SSID/key as I had used for the Guest SSID on my Orbi 5 system. Since the documentation noted the default VLAN profile was IOT(30), I didn't bother to confirm that setting prior to enabling and assumed all the devices I previously had connected to that SSID would just receive an IP in the range of 192.168.30.X. Instead, they all received a 192.168.1.X, at which point I checked both the Web GUI / Insight, which were showing the default VLAN profile was Default(1). I modified the VLAN profile accordingly and while some devices have now gotten an IP in the 192.168.30.X range, others are still showing a 192.168.1.X IP. In one case, I had a smart TV showing an IP in the .30.X range but then revert back to one in .1.X. Something really odd is going on here. Thoughts on next steps?
Issue 2 - No issues sending debug logs. Do you need from just main router or satellites (I have 2 of them) as well? For Insight, use the "Share Diagnostics" option within the Insight app?
Issue 3 - No issues providing this info as well.
It will take me a little time to gather everything but will send your way once I have it.
Thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
