WAN Drops Every Hour Exactly
Hi all!
I've been having an issue with my ER7206 dropping internet for about 10 seconds once an hour. It happens one hour apart exactly.
Topology is Nokia ONT to ER7206 to SG2428P to 2 EAP660HDs.
I've done a bit of research and my DHCP lease from my ISP is 2 hours. The internet drops at exactly the half-life of the lease. I did a packet capture and at the half-life, my gateway requests to extend the lease. The DHCP server sends an acknowledgment, then my gateway declines the ACK. At that point, the gateway sends a discovery request to the DHCP server and the DHCP server offers a new IP address. The gateway accepts the new IP address and that's when my internet drops.
I'm not sure if this is a known issue or not. I'd love some insight. Is there a setting I should change?
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @esiedlecki
Thanks for posting in our business forum.
esiedlecki wrote
My understanding (which could absolutely be wrong) is that the IP address indicated (216.115.0.108) is the DHCP server, and that 66.178.174.1 is the gateway. I will confirm with my ISP.
No. The ACK and DHCP offer are both coming from the ISP gateway. When the ER7206 declines that "UNKNOWN" DHCP server, it rediscovers and finds your ISP gateway which is the correct subnet and gateway IP.
This makes a full DHCP interaction. And this only happens when you are interacting with the 66.178.X.X gateway.
See the picture. When you regained your Internet, you were getting 66.178.X.X IP, is that correct? This should be the right IP address as far as I can tell.
Search your IP address in this Wireshark and see if this 66.178.X.X belongs to your ISP.
I am suspicious that you have an illegal DHCP server. Can you confirm the MAC address is not your Modem??
- Copy Link
- Report Inappropriate Content
Quick update - I went ahead and ran a packet capture with my Intel NUC connected directly to the ONT, ellimating all of my TP-Link equipment.
You can see here that it's a 2-hour lease just like when the ER7206 is plugged in. Also note that the DHCP server is indeed the address you were concerned about.
Here you can see that my NUC requests to extended the lease at the half-life of of the lease (just like the ER7206 does), and the DHCP server sends the ACK.
Here you can see that the lease gets extended by an hour, and the NUC keeps the original IP address.
From this, it looks to me like there is some problem with the interaction between the ER7206 and my ISP's DHCP server. I hope that's helpful info.
Also, I can confirm that that 66.178.x.x does belong to my ISP and is an expected IP address.
- Copy Link
- Report Inappropriate Content
I've gone ahead and switched from the ER7206 to a Ubiquiti Dream Machine Pro and the problem has stopped. This is clearly a problem with the ER7206. If the issue can be addressed and resolved, I'd love to return the UDM-Pro and stick with Omada.
- Copy Link
- Report Inappropriate Content
Hi @esiedlecki
Thanks for posting in our business forum.
esiedlecki wrote
I've gone ahead and switched from the ER7206 to a Ubiquiti Dream Machine Pro and the problem has stopped. This is clearly a problem with the ER7206. If the issue can be addressed and resolved, I'd love to return the UDM-Pro and stick with Omada.
I am still working with the senior engineer and requesting a response to this issue. Please bear with me for sometime before I get an answer from them.
We are setting up a network in our lab and trying to replicate this issue.
Will update you as soon as I get a response.
- Copy Link
- Report Inappropriate Content
Hi @esiedlecki
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address and escalated it to our support engineer to look into the issue. The ticket ID is TKID231213623, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Just curious as to if there were any resolutions to this problem...? I have the same problem as discussed in this thread and mentioned here ER7206 WAN Drops at Renew - Business Community (tp-link.com) and have opened ticket Number TKID240518991. I just started to troubleshoot the problem with support but wanted to save some time if possible. Similar to this person, if I switch back to my ER605, the problem dissappears. Fortunately my problem only occurs every 24 hours...
- Copy Link
- Report Inappropriate Content
Likely not what you want to hear, but I ended up moving away from Omada entirely and I now use Ubiquiti Unifi. It wasn't my ideal solution, but I don't get WAN drops every hour anymore. Unforuntalely TP-Link support was unable to provide a solution.
- Copy Link
- Report Inappropriate Content
@esiedlecki I sincerely appreciate you getting back to me so quickly! The issue seems to be limited to certain versions of tp-links routers as I don't seem to have this issue when using my older ER605.
Thanks Again!
- Copy Link
- Report Inappropriate Content
Hi @Aveamantium
Thanks for posting in our business forum.
Aveamantium wrote
Just curious as to if there were any resolutions to this problem...? I have the same problem as discussed in this thread and mentioned here ER7206 WAN Drops at Renew - Business Community (tp-link.com) and have opened ticket Number TKID240518991. I just started to troubleshoot the problem with support but wanted to save some time if possible. Similar to this person, if I switch back to my ER605, the problem dissappears. Fortunately my problem only occurs every 24 hours...
Case was not followed up after the ticket was created. And it was closed due to no replies.
- Copy Link
- Report Inappropriate Content
I suspect that the gateway at 67.178.174.1 is acting as a DHCP Relay agent and the real DHCP server is 216.115.0.108. Its quite common in an ISP scenario, because the actual DHCP server is not in the same subnet as the gateway and therefore isnt contactable directly by the broadcast DHCPDISCOVER.
Once the IP address has been allocated in the reply to the DHCPREQUEST, the actual DHCP server address is supplied. Subsequent IP renewal requests can be sent directly (unicast) to the actual DHCP server. This situation seems to be confusing the ER7206 in that it appears to believe that the original IP address was allocated by the relay agent ( 67.178.174.1) and that when it gets the same IP from the real DHCP server it rejects it and reverts to rediscovering.
A detailed view on the wireshark data from the DHCPOFFER and subsequent DHCPREQUEST and ACK would be useful to confirm...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2032
Replies: 22
Voters 0
No one has voted for it yet.