NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ORBI Network Dropping every 24hrs
Just recently installed an Orbi RBR50 in my house.I have AT&T Fiber, and after looking at suggestions online upgraded my AT&T Router to receive one with an IP Passthough. The AT&T moden was set up as...
highway wrote:Is there a way to get any more meaningful (more detail) logs out of Orbi? I'm pretty much in the blind.
Yes, there is a way to get more meaningful information from the Orbi, but it is neither quick nor easy.
Assuming this is a "version 1" Orbi with the USB port:
- Connect a USB memory stick with enough capacity to hold a full day's internal and external data.
- Go to the debug page (http://orbilogin.net/debug.htm)
- Check "Enable LAN/WAN Packet Capture"
- Select Store Location USB
- Click on "Begin Capture"
- Wait until the connection drops, which can be up to 24 hours.
The actual time should be found on the Orbi web interface, Advanced Tab,
click on the "Connection Status" box under "Internet Port"
the last item is "Lease Expires" - Once the Orbi loses connection, but is still running, return to the Orbi debug page,
Click on "Start Capture" to make it stop (crazy, right?)
Click on "Save Debug Log" - Remove USB memory stick from Orbi
- Insert USB memory stick into computer and there should be two folders:
LAN - every packet seen on the LAN side of the Orbi
WAN - every packet seen on the WAN side of the Orbi - Use a program that can display PCAP files (packet capture), such as Wireshark to open the WAN file.
- Create a display filter for "DHCP" packets only.
- There is supposed to be a request from the Orbi to renew the DHCP lease when the lease is half expired.
The DHCP server is supposed to respond to this request by renewing the lease. - If the lease is not renewed, the Orbi is to keep asking until the lease term actually expires,
at which time it is required by the standards to quit using this IP address and begin the DHCP request process from the start.
I just inserted a memory stick into my Orbi which reports 18 hr. 22 min remaining on a 24 hour lease. In about six hr. 22 min, I should be able to pull the USB stick and find the DHCP renewal packets. (Because mine works as expected.) In your case, when the Orbi loses connection, you should be able to document:
- Did my Orbi try to renew the DHCP lease as it is supposed to when half expired?
- Did the ISP respond as it is supposed to?
- When the lease term ran out, did my Orbi do what it was supposed to?
- etc.
Thank you for guidance CrimpOn I'll set this up today. The only thing is that I moved from DHCP so I only have connection time now. But I guess I'll try it both ways, there is nothing to loose anyway :)
My lease is almost due to renew. I am puzzled by this comment:
highway wrote:The only thing is that I moved from DHCP so I only have connection time now.
"moved from DHCP". You have set a static IP address in the Orbi? (or, what?) In the (very) short run, that might actually work. However, when the ISP decides to reallocate IP address pools and yours changes, the Orbi will suddenly stop working.
I can now report. After 6 hrs, 22 min (almost exactly) my Orbi sent a single DHCP unicast request to the ISP, the ISP immediately replied with a DHCP acknowledgement, and my lease was reset to 24 hours.
In other words, for this particular Orbi and this particular ISP, the DHCP renewal mechanism behaved exactly as described in the standards documents.
My netword is not especially active, and there was nobody at home for several hours. The USB stick still managed to accumulate over 213MB of WAN traffic and 1.3GB of LAN traffic.
I would dearly love to see a packet capture for an Orbi that consistently loses connection at the end of the DHCP lease. "Evidence" would be finding that either (a) the Orbi, or (b) the ISP did not generate requests or acknowledgements as expected. The Orbi should then return to broadcasting requests.
Yes, exactly. Sorry, I mentioned this in my first post. So I switched from DHCP to Static IP and it didn't help. I have static IP anyhow so it won't change. I left it at DHCP after reset that I made trying to fix this issue. This implies (at least I think so) the problem has nothing to do with the DHCP lease. There is something else. At least all the evidence and observations that I have points at this.
highway wrote:Yes, exactly. Sorry, I mentioned this in my first post. So I switched from DHCP to Static IP and it didn't help. I have static IP anyhow so it won't change. I left it at DHCP after reset that I made trying to fix this issue. This implies (at least I think so) the problem has nothing to do with the DHCP lease. There is something else. At least all the evidence and observations that I have points at this.
Please forgive my confusion. (I am terribly literal.) From this I conclude (1) you have secured a static IP from the ISP, but (2) the Orbi was left in DHCP mode, the default after a reset. So, the ISP knows you have a static IP and will not change it, but the Orbi does not know and is still using the DHCP mechanism to get its IP from the ISP (which is always the same).