Visitor
•
4 Messages
DHCP Lease lasting 2 Hours Max, disconnecting breifly in 30 minute, 1 hour intervals.
Using a R6700v2 Nighthawk router on the latest firmware, but I do not believe the model of the router is necessarily important.
This started happening 2-3 weeks ago, and I finally noticed it was disconnecting in the router logs, and further searching led me to similar cases by others finding it was due to the very very short DHCP leases. Obviously a lease changing happens sometimes, but it's not just doing it every 2 hours for me, rather intervals every 30 minutes or an hour on the dot (it's inconsistent) - see below
[Internet connected] IP address: Friday, April 14,2023 11:17:21
[Internet disconnected] Friday, April 14,2023 11:17:20
[Time synchronized with NTP server time-a.netgear.com] Friday, April 14,2023 10:17:37
[Internet connected] IP address: Friday, April 14,2023 10:17:20
[Internet disconnected] Friday, April 14,2023 10:17:19
[Time synchronized with NTP server time-b.netgear.com] Friday, April 14,2023 09:48:05
[Internet connected] IP address: Friday, April 14,2023 09:47:20
[Internet disconnected] Friday, April 14,2023 09:47:19
[Time synchronized with NTP server time-b.netgear.com] Friday, April 14,2023 08:48:00
[Internet connected] IP address: Friday, April 14,2023 08:47:21
[Internet disconnected] Friday, April 14,2023 08:47:19
[Time synchronized with NTP server time-a.netgear.com] Friday, April 14,2023 08:17:30
[Internet connected] IP address: Friday, April 14,2023 08:17:20
[Internet disconnected] Friday, April 14,2023 08:17:19
[Time synchronized with NTP server time-a.netgear.com] Friday, April 14,2023 07:17:23
[Internet connected] IP address: Friday, April 14,2023 07:17:19
[Internet disconnected] Friday, April 14,2023 07:17:18
[Time synchronized with NTP server time-b.netgear.com] Friday, April 14,2023 06:54:11
[Internet connected] IP address: Friday, April 14,2023 06:47:19
[Internet disconnected] Friday, April 14,2023 06:47:18
Here is my lease information:
DHCPServer : | (redacted) |
DNSServer : | |
Lease Obtained | 0 days,0 hrs,59 minutes |
Lease Expires | 0 days,0 hrs,38 minute |
For most use cases I would not even notice this, as the disconnect on the router lasts only a couple of seconds, but if I'm playing certain games, or my remote VPN connection is on for work certain things get disconnected (which was the exact reason that I ditched T-mobile internet back to xfinity)
I've looked over the similar cases here in the forums and know that it can be caused by maintenance/upgrades on the network in the area but I haven't seen anything about that and it's been going on for a few weeks now. I also know that there isn't a way for me to change the DHCP time on my end.
user_2881f3
Visitor
•
3 Messages
2 years ago
Good luck getting a response. I contacted support for this same issue a few weeks ago and have been jerked around since then. Originally support said it was because I was on a lower speed plan (75Mbps) and tried to upgrade me to a higher speed plan, obviously speed has nothing to do with this issue. Multiple devices provided by Xfinity with the same issue. Support was unwilling or unable to provide technical answers and would not escalate. They also apparently do not know if any work is happening in local areas. All around pretty useless.
0
0
CCKorie
Problem Solver
•
1.1K Messages
2 years ago
Hey there! I am sorry to hear you are having this sort of issues. I can understand how frustrating that may be. We are here to help, and would love to look into this for you. Can you send us a Dm with your name and address?
Here's the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the “chat" icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message
3
0
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
"Unsupported" doesn't matter on a lease time. The lease is controlled by the server upstream from you. It can be all over the map if they are working on stuff locally in your neighborhood, and might be a good indication that you are going to migrate to another IP address or subnet. On my stuff on the external WAN (bridge mode):
#cat dhclient.leases.em0 | grep dhcp-lease-time
option dhcp-lease-time 7200;
option dhcp-lease-time 3601;
option dhcp-lease-time 7200;
option dhcp-lease-time 3600;
option dhcp-lease-time 14230;
option dhcp-lease-time 14400;
option dhcp-lease-time 14400;
option dhcp-lease-time 18001;
option dhcp-lease-time 345600;
option dhcp-lease-time 345600;
option dhcp-lease-time 345600;
What can happen is IPV6 can get wrapped around the axle. Then that breaks routing for clients. It was a problem at my location for quite some time, although they seem to have fixed their end and it works better these days.
* I should add, when DHCPv6 was "broken", my work around was to just disable IPV6 entirely on the WAN interface, and it worked fine -- if you have that option with your gear.
(edited)
1
0