NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Odd problems with an R7000
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 i...
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?
> 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?
antinode wrote:> 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?