This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I've found a few problems. On the V1.0.9.12_1.2.23 right now, and was on it when I discovered a 'problem'. I backtracked to V1.0.9.10 and discovered another problem.
The 'new' problem is that I can NOT reset the R7000? At least I don't think I am (while on both of the above releases). I did the usual 30-30-30 deal. Router reboots with ALL settings intact? I recall in the past when I did this the base version installed when doing the 30-30-30 booted but with NO settings? I did have an older problem (https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7000-Reset-button-doesn-t/td-p/1037598) I posted here with a similar problem, but I am using a paper clip? Could the button not be working? I do see flashing lights so something is happening (maybe just a plain old reboot?)? Could the V1.0.9x firmware not allow a reset?
The other problem, a clear mismatch between the R7000 and Win10 what they think the IP Address Lease time is.
The R7000 from the ADVANCED page CONNECTION STATUS:
The difference seems to be causing the R7000 to ask for a renew of the IP Address and a Time Synch about a little over 1 hour all day long. This seems to possibly cause some delays in our Internet usage when it happens?
IF YOU HAVE AN R7000 ON THE SAME FLASH COULD YOU PLEASE CHECK THESE TWO ITEMS???
@JamesGL, I finally got the ISP to see it was somewhere on their side. Had to remove the router and use just the modem and the problem was still there. Lease time only 2 hours or less.
On a related note I see the latest flash has a fix for when it renews a lease.
- Fixes the issue where Internet sessions are disconnected when the DHCP lease update occurs on the Internet port.
It was probably that that made me notice I had a problem since it was happening every hour or so and sometimes browsing hung for a short period or reported a connection was broken?
Well, solved the RESET problem basically. I used the ADVANCED function BACKUP SETTINGS to ERASE the settings and revert to factory defaults. Worked, when I tried to access the router it worked like it was a new router. Asked for all data to be entered via Genie, even register the router. Checked and everything was cleared and set to a default. Could it be that is the only way to reset a router now? Button did NOT work?
That was the GOOD news. Bad news, the IP ADDRESS lease time is still less than 2 hours...
If you are READING this, have an R7000, please check your LEASE TIMES on the ADVANCED TAB under INTERNET PORT and select CONNECTION STATUS. Please REPLY here, no matter what you see? As I understand this the ISP sets it (it is the server) and the router is the client and asks for it, usually 1/2 the time the lease is set for. The router doesn't set the lease duration, the ISP does. If you've got similar results to what I'm seeing, and I am correct as to who sets the lease duration, there is a problem within the flash for the R7000. However W10 gets the lease details it always shows a 24 hour lease vs. the R7000 showing 2 hours or less.
> The other problem, a clear mismatch between the R7000 and Win10 what > they think the IP Address Lease time is.
Are you comparing the router's WAN/Internet interface with the Windows-system network interface? Why should they be similar? The router's WAN interface gets its data, including the public IP address, from the ISP DHCP server. The Windows system gets its data from the router's (LAN) DHCP server, which is entirely independent from the ISP.
The addresses differ, the subnets differ, the DHCP servers differ. Why should the lease times match?
> The other problem, a clear mismatch between the R7000 and Win10 what > they think the IP Address Lease time is.
Are you comparing the router's WAN/Internet interface with the Windows-system network interface? Why should they be similar? The router's WAN interface gets its data, including the public IP address, from the ISP DHCP server.
The addresses differ, the subnets differ, the DHCP servers differ. Why should the lease times match?
Yes, I agree with where each gets the Lease info.
The question is why are they different?
Again, which is what I'm having a problem with, what is shown on the Router in the Advanced tab's Connection Status? For instance,
Lease Obtained
0 days,1 Hours,57 Minutes
Lease Expires
0 days,1 Hours,2 Minutes
Did that not come from the ISP as you say? If not, why is the router placing various times (usually less than 2 hours and more than 1 hour) on the lease length? My ISP claims that this is NOT their problem. They have (and always have had) 24 hour leases. So if the ISP has a 24 hour lease period, why does the R7000 think it is less than 2 hours?
So you say " The Windows system gets its data from the router's (LAN) DHCP server, which is entirely independent from the ISP." OK, but if that is the case, then if the Router shows me a lease period of less than 2 hours, wouldn't W10's IPCONFIG show the same matching info? It doesn't:
Lease Obtained. . . . . . . . . . : Wednesday, November 29, 2017 9:10:26 AM Lease Expires . . . . . . . . . . : Thursday, November 30, 2017 9:10:25 AM
The two just don't match? As I see it, the client is the router and the server is the DHCP server on my ISP's network. So the Router should be doing what it is doing, but the question is WHY is the Router showing a lease period of less than 2 hours? So again, if you are right above, the router's (LAN) DHCP server KNOWS it has a 24 hour lease? Why then does it think it has a less than 2 hours lease and asked for a RENEW every 1 1/2 hours or so? Would this NOT be a bug in the Firmware?
Other possibility, my Router is 'bad' and processing the data wrong.
Do you have an R7000? What does your data look like?
That may be _your_ question. My question is: Why should the lease times match?
The router's WAN interface talks to your ISP, or at least to some other gizmo which talks to your ISP. The properties of that connection are negotiated between the router and the upstream DHCP server (at the ISP, or other intermediate gizmo).
The Windows system network interface talks to your router. The properties of that connection are negotiated between the Windows system and the DHCP server in your router.
The two DHCP servers have no direct communication with each other. I see no reason to expect the lease-time parameters of these two independent DHCP servers, dealing with two independent sub-networks, to be correlated in any way.
Netgear R7000 firmware offers no convenient user-interface method to change the parameters of its DHCP server, so there's not much which you can (easily) do to adjust them. The upstream DHCP server (at the ISP or other intermediate gizmo) may also be beyond your control (depending on what any intermediate gizmo might be).
> So you say " The Windows system gets its data from the router's (LAN) > DHCP server, which is entirely independent from the ISP." OK, but if > that is the case, then if the Router shows me a lease period of less > than 2 hours, wouldn't W10's IPCONFIG show the same matching info?
Why should it? You're looking at two different interfaces on two different systems, dealing with two different DHCP servers. The WAN interface on the router deals with one DHCP server. The Windows system's network interface deals with another (the router's) DHCP server.
> The two just don't match?
Why should they? Everything about them is different.
> As I see it, the client is the router and the server is the DHCP > server on my ISP's network. So the Router should be doing what it is > doing, but the question is WHY is the Router showing a lease period of > less than 2 hours?
That's an argument between you and your ISP (or other intermediate gizmo). I have no knowledge of or control over that DHCP server.
> So again, if you are right above, the router's (LAN) DHCP server KNOWS > it has a 24 hour lease?
The router's DHCP server "has" no lease on anything. A network _interface_ can have a lease on an IP address. The router's WAN interface gets an address from an upstream DHCP server, and there's some lease-time associated with that reservation.
The Windows system network interface gets an address from the router's DHCP server, and there's some lease-time associated with that reservation, normally determined by the router's DHCP server. The Windows system deals exclusively with the router's DHCP server; it has no dealings with any other upstream DHCP server. The router's DHCP server deals with its clients; it has no dealings with any other upstream DHCP server.
> Do you have an R7000? What does your data look like?
Not at the moment; only a D7000. My "Connection Status" pop-up shows nothing about the WAN DHCP parameters.
If it's not too much of an intrusion, why do you care about the lease-time of any of these DHCP address reservations?
I'll answer the last question first... why do I care...
Well as I mentioned before this constant every hour and a half RENEW started mid-day 11/15. We've been have some 'delays' at time using the internet, web browsing, program operations, etc. The browsing at times gave us an error that the channel was closed, or something like that. I attribute that to RENEW process and/or the router waiting to see if it has the same IP Address? These 'hiccups' in usage of the internet or so rare I'd admit, and may have nothing to do with the 'problem'.
Now as I see it:
ISP DHCP <----> Router <---> My PC
That is the Router gets the IP Address from my ISP's DHCP Server as well as the terms of the lease.
The Router stores that info internally and at the 1/2 time will issue a RENEW (this is quite normal).
Win10's IPCONFIG interogates the Router's DHCP Client for the Lease data.
Since the PC doesn't (at least I don't think it does) get to the ISP's DHCP Server but the DHCP Client on the Router how does it get a different set of Lease data than is DISPLAY by the Router on its Connection data page? Clearly the Router is acting in terms of the the data it displays for the lease. Almost hourly RENEWS.
So that leaves me with 3 possibilities:
The ISP is providing the Lease time of less that 2 hours (they say they are not)?
The Router is somehow storing the returned lease data wrong (firmware bug)?
As for W10's IPCONFIG, well it just gets the last time a lease was gotten and adds 24 hours to that and calls that the lease end.
So... one thing I'd like to do is THANK YOU for making me 'look'.
To confirm #3 I just did an IPCONFIG. Guess what, it is DIFFERENT from my other post today:
So I am now left with either my ISP has a problem and is lying to me or there is a s/w problem on the router. My router log matches the above for the last RENEW and Time Sync.
I guess it is up to me to prove my ISP right or wrong? When all the Internet traffic dies down here I might install my backup router and see if I see the same problem? Not sure it has the same logging functions though? That is why I was hoping someone with an R7000 could do the check for me on their network. Have the same indications, firmware bug. Don't, I have to convince the ISP they are the problem....
> 3. Win10's IPCONFIG interogates the Router's DHCP Client for the Lease > data.
The Windows system deals with the router's DHCP _server_.
> Since the PC doesn't (at least I don't think it does) get to the ISP's > DHCP Server but the DHCP Client on the Router [...]
The Windows system can't get to the upstream DHCP Server. It can get to the DHCP _server_ on the router.
> [...] how does it get a different set of Lease data than is DISPLAY by > the Router on its Connection data page?
The router gets its address (and related parameters) from the upstream DHCP server. The Windows system gets its address (and related parameters) from the router's DHCP server. These two DHCP servers have nothing to do with each other. They're on different sub-networks.
> 3. Win10's IPCONFIG interogates the Router's DHCP Client for the Lease > data.
The Windows system deals with the router's DHCP _server_.
> Since the PC doesn't (at least I don't think it does) get to the ISP's > DHCP Server but the DHCP Client on the Router [...]
The Windows system can't get to the upstream DHCP Server. It can get to the DHCP _server_ on the router.
> [...] how does it get a different set of Lease data than is DISPLAY by > the Router on its Connection data page?
The router gets its address (and related parameters) from the upstream DHCP server. The Windows system gets its address (and related parameters) from the router's DHCP server. These two DHCP servers have nothing to do with each other. They're on different sub-networks.
Yes, and that proves my point. W10's IPCONFIG's output it seems only gets the Router's time it got the lease, NOT the expiration time.
Modem Log entry:
11/30/2017 7:43
4000960006
New time has been retrieved from ToD server.
Time and Date:
Thu 2017-11-30 08:09:19
Router Lease data
Lease Obtained
0 days,1 Hours,38 Minutes
Lease Expires
0 days,1 Hours,28 Minutes
Current Time: Thursday, 30 Nov 2017 08:09:14
IPCONFIG data
Lease Obtained. . . . . . . . . . : Thursday, November 30, 2017 7:45:54 AM Lease Expires . . . . . . . . . . : Friday, December 1, 2017 7:45:53 AM
The current time is: 8:09:31.44
As you can see the PC (IPCONFIG) did not get the expire time it appears and just used the standard 24 hours. Easily proved too, if I wait say 2 hours, the router will do the renew and have a new lease, and again, the obtained times will match, but not the expire time on the PC.
@JamesGL, I finally got the ISP to see it was somewhere on their side. Had to remove the router and use just the modem and the problem was still there. Lease time only 2 hours or less.
On a related note I see the latest flash has a fix for when it renews a lease.
- Fixes the issue where Internet sessions are disconnected when the DHCP lease update occurs on the Internet port.
It was probably that that made me notice I had a problem since it was happening every hour or so and sometimes browsing hung for a short period or reported a connection was broken?
