NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
donawalt
Aug 11, 2024Mentor - Experienced User
Another bug? Router does not see the manual IP address
Check this image out. I have my MacBook Pro set with a manual address - 192.168.1.154. Yet the router admin web page Attached Devices, and the Orbi app, show it as 192.168.1.22 - an automatic IP/DHC...
donawalt
Aug 11, 2024Mentor - Experienced User
Ah! It just flipped back to the WiFi/automatic IP address (.72) again!
FURRYe38
Aug 11, 2024Guru - Experienced User
Looks like this is happening on the 770 series as well.
Here is my iPhone 12 Pro Max, Private WiFI address disabled, static IP set for .22.
RBR IP address range set for .100 thru .150 here.
It's appearing in the RBS web page as .108 along with the connection status reporting as 6Ghz only? I know thats wrong. I need to find out whats at .107 thats on 6G only. I presume thats incorrect as well.
I'll have to forward this on as I can't do more until mid week.
- donawaltAug 12, 2024Mentor - Experienced User
This is wild, check this test out - FURRYe38 maybe see if this happens on the 770 in addition to my test on the 970?
I have DHCP IP range set up as .2 -> .150. iPhone has a manual IP address of .156. iPad has a manual IP address of .152.
In the router devices list (and at all times the router device list is matched in the Orbi app's device list), the iPad shows as .152. The iPhone shows as .27.
To avoid having the devices come back online with an automatic/DHCP IP address, I turn off WiFi on the iPhone - I wait about 3-4 minutes, until it shows as disconnected in the Orbi app device list. I then delete the device from the list (you can only delete it if it is disconnected). I turn WiFi back on. It initially comes online as .156 correctly, in the router Device List, but in about 2-3 minutes it shows as .72!
So I do the same process again - turn off iPhone WiFi, wait, delete the entry in Orbi app device list, turn on ip. I go away, come back in about 15 minutes, and wow! The iPhone is still on .156! So I am thinking all is well.
EXCEPT - I check the router device list - iPhone is still on .156. What's on .72 now, I wonder? Yep - iPad!
So I do the same thing on the iPad - turn off iPad WiFi, wait, delete the entry in Orbi app device list, turn on ip. I check the device list about 10 minutes later, iPad is still correctly showing as .152. What's on .72? Yep - iPhone ☹️
I give up...this seems like more than just some old entries in the ARP table to me.
- CrimpOnAug 12, 2024Guru - Experienced User
Is this an intellectual exercise, or is there some reason to define a static IP on the iPad / iPhone rather than create entries in the LAN setup table for those devices?
p.s. I absolutely adore technical experimentation.
- donawaltAug 12, 2024Mentor - Experienced User
No, necessity. The devices I put on manual IP flood the router with DHCP requests - the Orbi 850, 960, and 970. Sometimes close to a 100 DHCP requests an hour. I don't know if it's an Apple, NG, or both problem. But it's been there for quite awhile.
- FURRYe38Aug 12, 2024Guru - Experienced User
Some devices support using Static IP address configurations. Like my D-Link cameras and NAS, I have them set to Static IPs for ease of management, use and connections. Those do appear correctly on the routers web page. We expect the same for all other devices, should users desire to put a static IP address on there devices. The configuration should appear correctly on the router or RBS web pages as well. Not appear to have differences in between.
- CrimpOnAug 12, 2024Guru - Experienced User
donawalt wrote:
No, necessity. The devices I put on manual IP flood the router with DHCP requests - the Orbi 850, 960, and 970.
Actually, 100 DHCP requests per hour is a trivial amount of bandwidth. The major irritation would be filling up the Orbi log file.
It would be fascinating to capture the DHCP conversations between the Orbi and these two specific devices. (It is SO frustrating how difficult it is to work with WiFi devices compared to Ethernet.)
- CrimpOnAug 12, 2024Guru - Experienced UserNo Apple devices.
- FURRYe38Aug 12, 2024Guru - Experienced User
Ok so this is happening on a Samsung Galaxy Tab 7 FE (Android) as well if I set it to a static IP address (192.168.0.22) that is outside of the current default IP address range on the RBR770. It briefly appeared on the RBRs web page then disappeared. I found the pads MAC address on the DR RBS however the IP address seen there is .105 and Connection Type is 6G Only. Pad doesn't support 6Ghz. RBS are ethernet connected to the RBR.
Also the .107 Address I found is a Amazon Echo Dot Gen 2. IP address is correctly reporting on the RBS web page however, Connection Type is not correct, Dots are not 6Ghz supporting. The other Echo Dot is reporting correctly at the RBR. The device listed with .241 IP address is a old NG WNHDE111 wireless bridge that has a static IP address configured on it. It's reporting the IP address correctly, however, Connection Type is not correct, This wireless bridge is not 6Ghz supporting. - CrimpOnAug 13, 2024Guru - Experienced User
FURRYe38 wrote:
Android?
This is SO COOL. It had never occurred to me that it is possible to define Static vs. DHCP by individual WiFi networks.
My Android tablet was dead and will test it when it charges for a while.
Tried a Chromebook on the RBR750 (no WiFi6E or WiFi7 here). Set to Static IP outside the DHCP range. The RBR750 picked up the Static IP immediately. Connected Chromebook to the RBR50 and watched it drop off the RBR750 Attached Devices. Connected back to RBR750 and it comes up with the Static IP. Connected to Guest WiFi and it got IP using DHCP. Back to primary WiFi and the Static IP comes up.
Will report how the Samsung Galaxy tablet does with Static IP when it charges enough to test. Not expecting anything unusual as this phenomenon appears to be limited to routers supporting 6G frequencies.
- donawaltAug 13, 2024Mentor - Experienced User
I have a number of devices that do not show this problem - 2 MacBook Pros, an old iPad, and old iPhone SE. So it's not all devices.
- CrimpOnAug 13, 2024Guru - Experienced User
Is the common factor 6G WiFi?
- donawaltAug 13, 2024Mentor - Experienced User
I can’t speak for Furrys android phones, but my iPad and iPhone that are doing this are 6E capable. But I do have that turned off.
- CrimpOnAug 13, 2024Guru - Experienced User
As expected, the Samsung Galaxy Tab S6-lite handles Static IP as expected.
With DHCP being the main issue, it would be really interesting to capture the traffic between those two devices and the DHCP server. My guess is there is no facility to capture the DHCP information directly on the iPad or iPhone, and the Orbi debug option does not record WiFi traffic.
I would consider using an Ethernet connected DHCP server to capture the request/reply for the iPad and iPhone. (Pi-Hole has a DHCP option).
- Roc1Aug 13, 2024LuminaryI have all my devices that connect to my 971 a reserved DHCP assigned IP. The RBE App always shows the same IP. Most all my connected devices are Arlo cams, keypads, sensors, chimes, doorbells , google smoke alarms , Schlage deadbolts. These IoT devices don’t show their assigned IPs, and you can’t use a GUI approach to get into them, so I don’t know if the Orbi app reserved IPs are what the device is using or not.
I also have 6E disabled on my only Apple device, but the 5Ghz is not handing off smoothly between nodes.
donawalt, are you staying in one spot while you are discovering this static IP bug, or moving between nodes?
I don’t know how DHCP IP and static ip’s work, but I think the 971 issue regardless of 5Ghz or 6Ghz band is that WiFi drops out frequently (moving between nodes, or not moving around. So the router “discovers a new device and says hey, it needs an IP. So it’s either not looking in your static IP address table first, it’s assigning a DHCP IP. But then, shortly (not on a predetermined time interval), the WiFi drops again, same flawed DHCP vs Static IP process happens again.
That’s probably why your log showed so many DHCP requests. Every time WiFi drops out, the router sees a “new device” and the bug IP assignment process starts anew.
Ever morning when I get up, my iPhone shows 5G cellular, it takes anywhere from 15secs to 2 mins to connect again to Orbi 5Ghz band (I have 6Ghz disabled). Something in these NG WiFi 7 mesh systems is not working correctly. - donawaltAug 13, 2024Mentor - Experienced User
Roc1 it’s independent of moving around for me.
Roc1 , TC_in_Montana tried to figure it out with debug logs, but eventually hit a brick wall, I think due to lack of documentation and help from NG.
- Roc1Aug 13, 2024Luminarydonawalt , Ok, I knew I’d checked this before, but I’d forgotten I had. The IP address my iPhone shows in Settings is the DHCP IP I have reserved in the 971 router. It has been that same Reserved IP shown on my iPhone since I installed the router in late May and reserved the DHCP IP after the router first assigned it to the phone, so my device IP’s aren’t all over the board like yours are!
I think my router is probably flooding DHCP requests too like you saw and switched to Static IP’s, but apparently every time the mesh WiFi 7 network drops my WiFi connection, the router sees my DHCP reservation and reassigns the same one, over and over again.
If these 971’s are going to continually drop WiFi, you might as well go back to Reserved IP’s until NG gets this IPV6, DhCP, Static IP issue fixed? At least you’ll know the devices IP, and your static IP’s apparently haven’t reduced the DHCP flooding anyway.
I will say your suggestion to disable 6E and stay on 5Ghz band is not perfect (and won’t be without firmware update), but it seems to be as “reliable” as this WiFi router can be at this point in time. - donawaltAug 13, 2024Mentor - Experienced User
HI Roc1 , a few things from your post:
1) You are using reserved IPs in the DHCP range. I am not. I am using manually entered IPs outside the DHCP range.
2) You may have DHCP flooding, as with reserved IP addresses the DHCP server, as part of the router, does have to serve up IP addresses. With a manual IP address, the DHCP is not involved. My DHCP flooding has been eliminated by using manual addresses.
3) I don't have any 5G "flips" or dropped connections with WiFi 6E turned off on my 2 mobile devices that support it - iPad and iPhone. The network has been rock-stable for me with that configuration!
I would like to see 6E work better in the next firmware update, which I suspect will be soon. It should be, especially with NG touting their WiFi 7 support in the 970 series, and with WiFi 7 devices coming...
- FURRYe38Aug 13, 2024Guru - Experienced User
So the static IP address set on the Samsung Galaxy Tab appears and displays as the static IP address number on the RBR750s web page? And not different?
CrimpOn wrote:
As expected, the Samsung Galaxy Tab S6-lite handles Static IP as expected.
With DHCP being the main issue, it would be really interesting to capture the traffic between those two devices and the DHCP server. My guess is there is no facility to capture the DHCP information directly on the iPad or iPhone, and the Orbi debug option does not record WiFi traffic.
I would consider using an Ethernet connected DHCP server to capture the request/reply for the iPad and iPhone. (Pi-Hole has a DHCP option).
- CrimpOnAug 13, 2024Guru - Experienced User
FURRYe38 wrote:
So the static IP address set on the Samsung Galaxy Tab appears and displays as the static IP address number on the RBR750s web page? And not different?
Exactly. My attempt to replicate the problem on the RBR750 with two devices connecting over WiFi with Static IPs (on the devices) resulted in the expected behavior: both appeared on the Orbi Attached Devices display with the Static IP.
It could be because these particular devices do not cause the problem or that the RBR750 does not work the same way as the 770 and 970 routers. The obvious difference is that 6G WiFi frequency is not present in any way.
- FURRYe38Aug 13, 2024Guru - Experienced User
Ok thank you. Seems that this only effects Orbi 770 and 970 series with Apple and Android devices thus far.
Not a 6Ghz relation since my iPhone and Android pad are not 6Ghz supporting.
Issue has been passed on to NG.