WAN Drop Outs

WAN Drop Outs

WAN Drop Outs
WAN Drop Outs
2024-02-12 10:37:33 - last edited 2024-02-18 02:38:58
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.3.0

At least once a week (often more), WAN connection will drop.

 

Either I have to log into the dashboard and click disconnect / connect, or I have to power cycle the controller OC200v1 and router.

 

Often the WAN status will say Online but the button will say connect, or the WAN status will say Offline, but the button will say disconnect.

  0      
  0      
#1
Options
1 Accepted Solution
Re:WAN Drop Outs-Solution
2024-02-18 02:38:18 - last edited 2024-02-18 02:38:58

Hi @philhumber 

Thanks for posting in our business forum.

Contact your ISP and consult this issue. It seems to be the ISP issue. The easiest way is to ask your ISP and about this modem.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
Recommended Solution
  0  
  0  
#2
Options
5 Reply
Re:WAN Drop Outs-Solution
2024-02-18 02:38:18 - last edited 2024-02-18 02:38:58

Hi @philhumber 

Thanks for posting in our business forum.

Contact your ISP and consult this issue. It seems to be the ISP issue. The easiest way is to ask your ISP and about this modem.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
Recommended Solution
  0  
  0  
#2
Options
Re:WAN Drop Outs
2024-02-18 19:15:27

  @Clive_A thanks, but this doesn't seem like an ISP issue. The ER605 is connected to a Nokia 5G modem mounted in a fixed location. When the WAN connection drops on the ER605, I connect to the 5G modem via Bluetooth using the Nokia diagnostic app and verify the 5G connection is still up. Every time the 5G modem is still maintaining it's connection and it's still connected with the uptime visible as multiple weeks and months. 

 

The ER605 is somehow dropping the connection to the 5G modem and is not able to restart the correction without me manually logging into the omada dashboard and clicking either "Disconnect" then "Connect" or just clicking "Connect" depending on how the ER605 / controller is behaving. 

  0  
  0  
#3
Options
Re:WAN Drop Outs
2024-02-19 01:03:28 - last edited 2024-02-19 01:04:28

Hi @philhumber 

Thanks for posting in our business forum.

philhumber wrote

  @Clive_A thanks, but this doesn't seem like an ISP issue. The ER605 is connected to a Nokia 5G modem mounted in a fixed location. When the WAN connection drops on the ER605, I connect to the 5G modem via Bluetooth using the Nokia diagnostic app and verify the 5G connection is still up. Every time the 5G modem is still maintaining it's connection and it's still connected with the uptime visible as multiple weeks and months. 

 

The ER605 is somehow dropping the connection to the 5G modem and is not able to restart the correction without me manually logging into the omada dashboard and clicking either "Disconnect" then "Connect" or just clicking "Connect" depending on how the ER605 / controller is behaving. 

TBH, if you don't think this is a problem with the ISP, then Wireshark and paste the result after using the "dhcp" as the filter.

With all the information you provided so far, I cannot make a judgment. It is a plain description with zero evidence showing me that the ER605 is to blame.

I met thousands of cases of WAN drops and most are ISP issues. Rarely that the issue from the router. I am not saying there is zero chance of having a software bug. But I don't think I can be of any help in your case.

 

Unless you can provide the following:

Is this a periodical drop?

Wireshark results that show the traffic behind WAN drops. (Key to this issue.)

Do you have a log from the ER605 at the timestamp of the WAN drops? Same to the 5G modem, is there a log system?

What are the ping results when the dropout happens? To default gateway, to 8.8.8.8 or any of the websites you frequently visit.

Modem uptime does not mean anything. It means the uptime of the booting. Or give me the screenshot of your diagnosis about this "uptime".

5G modem, signal strength? How can you be sure that the sim card is receiving the service perfectly fine with zero down or reconnect time?

What's the IP address on your WAN status when it is "drops"?

 

BTW, about the online or offline status on WAN, read this.

 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#4
Options
Re:WAN Drop Outs
2024-03-04 11:31:36

  @Clive_A Hi. Thanks for the reply.

 

From some further analysis and finding some related postings, it's starting to feel like an issue with the IP being refreshed from the modem. Each time the drop out happens, and I need to go back in and manually press connect the IP changes.  I found these related posts that seem to confirm similar behaviors and resolution. As a test, I placed a basic router between the 5G modem and the ER605 assigning a fixed internal IP to the 605 and the problem is resolved.  I understand this is anecdotal without the wireshark, but at least it's given a temporary workaround.

 

To be crystal clear - the issue specifically seems to be the ER605 losing the connection (for some reason - seems to be related to an IP change) and not being able to restore the connection itself. I need to log into the controller and press 'Connect' at which point WAN is restored, and all is well again.

 

Similar Issues:

https://community.tp-link.com/en/business/forum/topic/584784

https://community.tp-link.com/en/business/forum/topic/578060

https://community.tp-link.com/en/business/forum/topic/519916?replyId=1046062

 

Next step to confirm is to run the wireshark with a focus on DHCP as you suggest - which I will aim to do over the course of this week.

 

Regarding some other questions you asked:

 

Is this a periodical drop?

Seemingly random with no visible pattern.

 

Wireshark results that show the traffic behind WAN drops. (Key to this issue.)

As above, will provide.

 

Do you have a log from the ER605 at the timestamp of the WAN drops? Same to the 5G modem, is there a log system?

No ability to access logs from the 5G as the webUI cannot be accessed - only using a consumer bluetooth app. In the 605 logs, no visible errors. Log extract below, along with screengrab of WAN drop outs from alerts panel.
 

What are the ping results when the dropout happens? To default gateway, to 8.8.8.8 or any of the websites you frequently visit.

All failures. Ping results are fine within the network but anything outside fails.

 

Modem uptime does not mean anything. It means the uptime of the booting. Or give me the screenshot of your diagnosis about this "uptime".

Noted. My misunderstanding here. However, the signal remains strong and connected with the 5G modem. This is a Nokia modem, you can connect via bluetooth directly to it and see stats. Modem shows as connected with strong connection. Impossible to watch at the same time as a WAN disconnect happens on the 605, as it happens randomly.

 

5G modem, signal strength? How can you be sure that the sim card is receiving the service perfectly fine with zero down or reconnect time?

Based on best guesses. When the WAN drops, the mobile devices fall back to the same 5G network. This is a rurual location, with only one cell tower -  so it's just an assumption that the 5G is still operational.  However, this issue isn't regarding the down time - it's the fact that the 605 cannot automatically re-establish the connection without manually logging into the controller and physically clicking 'Connect'.

 

What's the IP address on your WAN status when it is "drops"?

Still shows the IP information including DNS but with a red 'Offline' status.  After pressing connect, IP is refreshed, and connection is 'Online' once again.

 

 

-------

 

 

WAN Errors:

 

 

Logs at the same time:

 

03-03-2024 20:02:10.305 INFO [client-schedule-statistic-task-0] [] c.t.s.o.c.d.a.s(): [STAT] {"wiredClients":9,"statName":"ClientStatInfo","authedClients":0,"wirelessClients":15}
03-03-2024 20:05:00.111 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:11:00.109 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:17:00.102 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:23:00.092 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:23:01.022 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (manager_vpn_certificate_clear, null) but did not execute because corresponding handler manager_vpn_certificate_clear doesn't exist
03-03-2024 20:29:00.092 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:35:00.119 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:41:00.101 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:41:42.928 WARN [client-inform-work-group-0] [] c.t.s.o.c.d.m.d.i(): Not the same connection and has changed before, create new clientHistory
03-03-2024 20:43:45.012 INFO [monitor-common-block-pool-14] [] c.t.s.o.m.d.c.a.a(): no msp history data found.
03-03-2024 20:47:00.139 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:53:00.092 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 20:59:00.089 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:02:03.291 INFO [https-jsse-nio-443-exec-8] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:02:10.465 INFO [client-schedule-statistic-task-0] [] c.t.s.o.c.d.a.s(): [STAT] {"wiredClients":9,"statName":"ClientStatInfo","authedClients":0,"wirelessClients":15}
03-03-2024 21:02:29.117 INFO [https-jsse-nio-443-exec-6] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:02:42.875 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:03:28.854 INFO [https-jsse-nio-443-exec-5] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:04:03.476 INFO [https-jsse-nio-443-exec-9] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:04:11.691 INFO [https-jsse-nio-443-exec-3] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:05:00.099 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:11:00.103 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:17:00.116 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:20:28.289 WARN [https-jsse-nio-443-exec-11] [] c.t.s.o.a.d.u.WebUtils(247): requestCSRFToken is not correct for request /api/v2/loginStatus
03-03-2024 21:21:16.408 INFO [https-jsse-nio-443-exec-5] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(62): NoSupport internal service for anomaly
03-03-2024 21:22:41.219 INFO [https-jsse-nio-443-exec-4] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:23:00.140 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:23:01.022 WARN [quartzScheduler_Worker-1] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (manager_vpn_certificate_clear, null) but did not execute because corresponding handler manager_vpn_certificate_clear doesn't exist
03-03-2024 21:23:12.874 INFO [https-jsse-nio-443-exec-10] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:29:00.096 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:31:28.797 INFO [https-jsse-nio-443-exec-10] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:31:52.454 INFO [https-jsse-nio-443-exec-1] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:32:22.713 INFO [https-jsse-nio-443-exec-8] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:33:32.797 INFO [https-jsse-nio-443-exec-5] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:34:00.715 INFO [https-jsse-nio-443-exec-6] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:34:05.193 INFO [https-jsse-nio-443-exec-11] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:34:56.687 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 21:35:00.098 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:41:00.115 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:43:45.008 INFO [monitor-common-block-pool-14] [] c.t.s.o.m.d.c.a.a(): no msp history data found.
03-03-2024 21:47:00.093 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:53:00.119 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:59:00.107 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 21:59:55.565 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:01:15.525 INFO [https-jsse-nio-443-exec-5] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:02:10.268 INFO [client-schedule-statistic-task-0] [] c.t.s.o.c.d.a.s(): [STAT] {"wiredClients":9,"statName":"ClientStatInfo","authedClients":0,"wirelessClients":15}
03-03-2024 22:03:00.095 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:09:00.105 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:15:00.103 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:21:00.101 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:23:01.022 WARN [quartzScheduler_Worker-1] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (manager_vpn_certificate_clear, null) but did not execute because corresponding handler manager_vpn_certificate_clear doesn't exist
03-03-2024 22:27:00.101 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:33:00.091 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:36:45.603 INFO [https-jsse-nio-443-exec-9] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:36:56.460 INFO [scheduled-pool-3] [] c.t.s.o.c.d.a.x(): client timeout 8A-C6-4E-52-B2-09
03-03-2024 22:37:12.900 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:37:43.166 INFO [https-jsse-nio-443-exec-10] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:38:09.274 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:38:55.609 INFO [https-jsse-nio-443-exec-5] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:39:00.090 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:40:30.780 INFO [https-jsse-nio-443-exec-7] [] c.t.s.o.a.a.i.h.HealthInternalAdapterConfiguration(68): NoSupport internal service for anomaly
03-03-2024 22:43:45.065 INFO [monitor-common-block-pool-7] [] c.t.s.o.m.d.c.a(): clear omadac data with omadacId [78ce5d2aac07e53fb59293489f54c141], mspId []
03-03-2024 22:43:45.303 INFO [monitor-common-block-pool-7] [] c.t.s.o.m.d.c.a.a(): no msp history data found.
03-03-2024 22:43:45.543 INFO [manager-data-retention-pool-0] [] c.t.s.c.u.l.LocalUpgradeFileCache(): delete expired upgrade file, number = 0
03-03-2024 22:45:00.099 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:51:00.096 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 22:57:00.090 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:02:10.267 INFO [client-schedule-statistic-task-0] [] c.t.s.o.c.d.a.s(): [STAT] {"wiredClients":9,"statName":"ClientStatInfo","authedClients":0,"wirelessClients":15}
03-03-2024 23:03:00.090 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:09:00.094 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:15:00.099 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:21:00.096 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:23:01.023 WARN [quartzScheduler_Worker-1] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (manager_vpn_certificate_clear, null) but did not execute because corresponding handler manager_vpn_certificate_clear doesn't exist
03-03-2024 23:27:00.100 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:33:00.093 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:39:00.096 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:41:56.529 INFO [scheduled-pool-8] [] c.t.s.o.c.d.a.x(): client timeout C0-48-E6-1D-2C-66
03-03-2024 23:43:45.009 INFO [monitor-common-block-pool-10] [] c.t.s.o.m.d.c.a.a(): no msp history data found.
03-03-2024 23:45:00.090 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:51:00.091 INFO [monitor-topology-pool-0] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
03-03-2024 23:57:00.100 INFO [monitor-topology-pool-1] [] c.t.s.o.c.u.e.a(314): list local interface macs: [10-27-F5-A2-05-8E]
 

  0  
  0  
#5
Options
Re:WAN Drop Outs
2024-03-05 01:34:17

Hi @philhumber 

Thanks for posting in our business forum.

I don't need the running log. That's only showing me the device status and log of controller adopted devices instead of your Internet.

This is key to me.

philhumber wrote

What's the IP address on your WAN status when it is "drops"?

Still shows the IP information including DNS but with a red 'Offline' status.  After pressing connect, IP is refreshed, and connection is 'Online' once again.

 

I will still hold my opinion that this is a problem with your ISP or modem. You don't have to Wireshark from the ER605 WAN because this clearly tells me that there is no DHCP issue with the ER605 WAN to the modem. IP and the rest of the stuff are still there, it just loses the Internet.

 

I don't think there is anything I can recommend as I have done that. About how it becomes offline and how the router determines it is offline, you can read the KB I wrote for load balancing and online detection. I will not repeat it here.

Case is closed for me at this moment. If you can overturn my judgment with some other evidence or compared results.

 

 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  1  
  1  
#6
Options

Information

Helpful: 0

Views: 218

Replies: 5

Related Articles