TP-Link Archer AX58 drops internet connection every 8 to 10 hours.LED goes red and then off
TP-Link Archer AX58 drops internet connection every 8 to 10 hours.LED goes red and then off
Hi
I have a similar problem to this thread on my Archer AX58 :
TP-Link Archer AX55 drops internet connection every 8 to 10 hours. All lights stay ON green.
https://community.tp-link.com/us/home/forum/topic/610734?sortDir=ASC
The only exception is that the LED showing connection to my DSL modem goes red and then off.
i.e. every 8-10hours the AX58 router drops the connection to my DSL modem.
I have even swapped out the DSL modem and no change.
The only workaround I have is to power-off / -on the AX58 router. I cannot see anything in the logs as these seem to get lost at power-off.
Please can you help out as my internet connection is essential as I work from home.
Thanks!
Andrew
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @anderigs, thank you very much for posting in the community.
The thread you're referring to is quite old and has been resolved via firmware upgrade as I mentioned in the reply.
If you're experiencing a similar issue with your AX58, please go through this thread to do some basic troubleshooting and get back with the requested details for further investigation:
- Copy Link
- Report Inappropriate Content
@Kevin_Z thanks for the fast response!
I am experimenting with one other topic (setting static IP address from ISP DSL modem for the AX58) - I need to wait 8-10 hours to see if this works. I was wondering if the there is some dynamic IP lease expiry timeout (this does not seem to be defined on the ISP DSL modem) which somehow causes this problem.
If not I will continue with the ideas in the useful link you posted.
I can already say:
1. internet connection is stable when the router is NOT connected - somehow attaching the router kills the internet connection. ISP has already checked everything there. ISP is A1 Telekom Austria.
2. I have tried different CAT6 cables - the current one is brand new
3. AX58 firmware is up to date - the ISP DSL modem firmware is updated automatically by the ISP
I will continue with the DNS and rest - or hopefully not! - in the next 8-10 hours.
THANKS!
Cheers,
Andrew
- Copy Link
- Report Inappropriate Content
Thank you very much for the detailed information.
Does A1 Telekom require you to configure a static IP address for the wireless router connected to it? What is the WAN Connection Type on the AX58? Is it Static IP?
You may contact A1 Telekom to check if there is anything that can be changed to optimize the connection status, such as using a dynamic IP address.
If possible, please check if the internet will be stable if you connect a switch between the A1 Telekom modem and the AX58. That is, A1 Telekom modem --- Switch --- AX58.
- Copy Link
- Report Inappropriate Content
Ok the static IP address did not work - - previously I had it set to dynamic and the problem still occured - in fact I realised later it was still "DHCP Static" - this time the connection was broken after 10hrs and 40mins after the last reboot.
On the AX58 I have dynamic IP. I just set the DNS IP 8.8.8.8 and 1.1.1.1 instead of picking up from ISP. Not sure how this will help.
When the Zyxel-AX58 connection is down I cannot login to AX58 from any of my LAN - the GUI shows but no password field and it says "operation failed". I have tried this at multiple occasions. I have never had another router between the Zyxel and my LAN - I added the AX58 as an extra layer of security AND to establish an easymesh Wifi network - previously the powerline and switch were attached directly to the Zyxel.
Here is a simple view of my network - as you can see apart from the Zyxel modem all products from TPLink:
So do you want me to try to put the TL-SG105 between the Zyxel and AX58?
Which "internet data" do you want precisely from the Zyxel?
- Copy Link
- Report Inappropriate Content
@Kevin_Z I cannot seem to resolve the issue. I have now just reconnected an old router that I retired about 6 months back (it never had any problems) to see if I can find any differences in the network settings and I couldn't find a thing.
I have dynamic IP address set on my old router, the AX58 and on the Zyxel.
Below I have added the syslog from the AX58 during connection setup - from what I can see during startup all looks ok.
What else can I do?
As said it is impossible to login to the AX58 after it has lost the internet connection so at this point I cannot retrieve the logs - this seems to be a really bad design decision to need internet connectivity to authenticate a login. Is there any way to ssh or telnet into the AX58 when it has lost the internet connection?
Thanks for any pointers...
--- syslog---
####################################################################
# Archer AX58 System Log
# Time = 2024-07-24 22:10:36
# H-Ver = 2.0.0 ; S-Ver = 1.0.3 Build 20240123 rel.24345
# LAN: I = 192.168.0.1 ; M = 255.255.255.0 ; MAC = 20:23:51:11:EF:E0
# WAN: W = dhcp ; I = 10.0.0.108 ; M = 255.255.255.0 ; MAC = 20:23:51:11:EF:E1
# G = 10.0.0.138 ; D1 = 8.8.8.8 ; D2 = 1.1.1.1
# Clients connected: 6 ; WI-FI : 4
####################################################################
2024-07-24 22:07:35 traffic-stats[2561]: <6> 269004 stats reset
2024-07-24 22:07:35 network[2003]: <6> 290005 Reload config
2024-07-24 22:07:33 network[2003]: <6> 290130 Set IPv6 status to off, protocol is <null>
2024-07-24 22:07:21 traffic-stats[2561]: <6> 269004 stats reset
2024-07-24 22:07:21 network[1357]: <6> 290005 Reload config
2024-07-24 22:07:20 network[1357]: <6> 290130 Set IPv6 status to on, protocol is <null>
2024-07-24 18:26:35 led-controller[1217]: <6> 288051 Start to run WAN1_ON
2024-07-24 18:26:35 led-controller[1217]: <6> 288051 Start to run WAN0_OFF
2024-07-24 18:26:35 led-controller[1217]: <6> 288051 Start to run LAN_ON
2024-07-24 18:26:01 upnp[2362]: <6> 217504 Service start
2024-07-24 18:26:01 upnp[2362]: <6> 217505 Service stop
2024-07-24 18:26:00 led-controller[1217]: <6> 288051 Start to run WAN1_ON
2024-07-24 18:26:00 led-controller[1217]: <6> 288051 Start to run WAN0_OFF
2024-07-24 18:26:00 led-controller[1217]: <6> 288051 Start to run LAN_ON
2024-07-24 18:25:57 remote-management[1906]: <6> 282505 Service stop
2024-07-24 18:25:48 qos[877]: <6> 259504 Service start
2024-07-24 18:25:48 nat[3902]: <6> 211021 IPSEC ALG enabled
2024-07-24 18:25:48 qos[877]: <6> 259503 Function disabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 L2TP ALG enabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 PPTP ALG enabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 SIP ALG enabled
2024-07-24 18:25:48 qos[877]: <6> 259505 Service stop
2024-07-24 18:25:48 nat[3902]: <6> 211021 RTSP ALG enabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 H323 ALG enabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 TFTP ALG enabled
2024-07-24 18:25:48 nat[3902]: <6> 211021 FTP ALG enabled
2024-01-23 00:01:31 nat[3902]: <6> 211501 Initialization succeeded
2024-01-23 00:01:30 nat[3902]: <6> 211501 Initialization succeeded
2024-01-23 00:01:27 led-controller[1217]: <6> 288051 Start to run WAN1_OFF
2024-01-23 00:01:27 led-controller[1217]: <6> 288051 Start to run WAN0_ON
2024-01-23 00:01:27 led-controller[1217]: <6> 288051 Start to run LAN_ON
2024-01-23 00:01:27 dhcpc[3799]: <6> 210054 receive ack from server with ip 10.0.0.108, options(serverid=10.0.0.138;lease=86400;subnet=255.255.255.0;router=10.0.0.138;dns=10.0.0.138;)
2024-01-23 00:01:26 dhcpc[3799]: <6> 210053 send select request with options(cliid=01/20:23:51:11:ef:e1:;reqip=10.0.0.108;serverid=10.0.0.138;)
2024-01-23 00:01:26 dhcpc[3799]: <6> 210052 receive offer from server with ip 10.0.0.108, options(serverid=10.0.0.138;lease=86400;subnet=255.255.255.0;router=10.0.0.138;dns=10.0.0.138;)
2024-01-23 00:01:26 dhcpc[3799]: <6> 210051 send discover with ip 0.0.0.0 and flags 0
2024-01-23 00:01:25 led-controller[1217]: <6> 288051 Start to run WAN1_OFF
2024-01-23 00:01:25 led-controller[1217]: <6> 288051 Start to run WAN0_OFF
2024-01-23 00:01:24 led-controller[1217]: <6> 288051 Start to run LAN_OFF
2024-01-23 00:01:22 led-controller[1217]: <6> 288051 Start to run STATUS_ON
2024-01-23 00:01:21 qos[3362]: <6> 259504 Service start
2024-01-23 00:01:21 qos[3362]: <6> 259503 Function disabled
2024-01-23 00:01:21 led-controller[1217]: <6> 288051 Start to run GENERAL
2024-01-23 00:01:16 traffic-stats[2547]: <6> 269504 Service start
2024-01-23 00:00:54 factory-reset[1157]: <6> 284504 Service start
2024-01-23 00:00:53 parental-control[828]: <6> 229504 Service start
2024-01-23 00:00:53 parental-control[828]: <6> 229502 Function enabled
2024-01-23 00:00:51 access-control[618]: <6> 239504 Service start
2024-01-23 00:00:51 access-control[618]: <6> 239503 Function disabled
2024-01-23 00:00:49 nat[3937]: <7> 211001 Flush conntrack
2024-01-23 00:00:49 nat[3937]: <6> 211502 Function enabled
2024-01-23 00:00:49 nat[3937]: <5> 211051 Create NAT chain succeeded
2024-01-23 00:00:47 nat[3937]: <6> 211501 Initialization succeeded
2024-01-23 00:00:47 nat[3937]: <6> 211501 Initialization succeeded
2024-01-23 00:00:45 basic-security[3435]: <6> 219504 Service start
2024-01-23 00:00:45 basic-security[3435]: <5> 219606 Flush conntrack table succeeded
2024-01-23 00:00:43 firewall[2448]: <6> 209504 Service start
2024-01-23 00:00:16 led-controller[1217]: <6> 288051 Start to run WIFI5G_ON
2024-01-23 00:00:16 led-controller[1217]: <6> 288051 Start to run WIFI2G_ON
2024-01-23 00:00:08 imb[2696]: <6> 218507 Daemon connection succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.91 and MAC 2C-60-0C-1C-DD-E6 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.28 and MAC F8-16-54-2F-F1-61 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.44 and MAC 9C-A2-F4-CA-C6-A3 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.232 and MAC 74-FE-CE-2E-9C-FC bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.27 and MAC F8-16-54-2F-F1-61 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.190 and MAC 80-3F-5D-F8-E8-62 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.45 and MAC 40-F8-DF-10-6C-72 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.156 and MAC 6A-A0-32-9D-85-A2 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.41 and MAC 5E-65-C8-7A-43-09 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.103 and MAC FC-65-DE-56-67-CF bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.210 and MAC FC-65-DE-39-FE-A6 bound succeeded
2024-01-23 00:00:08 imb[2696]: <5> 218021 IP 192.168.0.83 and MAC 68-1D-EF-36-EC-70 bound succeeded
2024-01-23 00:00:08 imb[2696]: <6> 218506 Config interface initialization succeeded
2024-01-23 00:00:08 imb[2696]: <6> 218011 ARP Binding enabled
2024-01-23 00:00:08 imb[2696]: <6> 218506 Config interface initialization succeeded
2024-01-23 00:00:08 imb[2696]: <6> 218501 Initialization succeeded
2024-01-23 00:00:07 upnp[2561]: <6> 217504 Service start
2024-01-23 00:00:07 upnp[2561]: <6> 217505 Service stop
2024-01-23 00:00:05 remote-management[2104]: <6> 282505 Service stop
2024-01-23 00:00:04 dhcpc[1865]: <6> 210056 teardown and release
2024-01-23 00:00:03 dhcpc[1865]: <6> 210051 send discover with ip 0.0.0.0 and flags 0
2024-01-23 00:00:00 time-settings[1284]: <6> 279504 Service start
1970-01-01 00:00:25 led-controller[1217]: <6> 288051 Start to run STATUS_SAN
1970-01-01 00:00:24 led-controller[1217]: <6> 288504 Service start
- Copy Link
- Report Inappropriate Content
@anderigs Thanks a lot for providing all these details.
So you're confirming that the AX58 is getting a WAN IP address from the Zyxel modem but not using a static IP address, right?
Can you please confirm again what is the LED status on the AX58 when the connection is down and you're no longer able to login to the web interface page of the AX58?
If possible, could you please try to disconnect the powerline devices and the SG105 switch from the network, and connect your phone or computer directly to the AX58, then check if you can get a stable connection and login to its web management page anytime?
- Copy Link
- Report Inappropriate Content
So you're confirming that the AX58 is getting a WAN IP address from the Zyxel modem but not using a static IP address, right?
Yes. From what I can see via udhcp which I have enabled on the AX58.
Can you please confirm again what is the LED status on the AX58 when the connection is down and you're no longer able to login to the web interface page of the AX58?
Here is the LED status when the problem has happened:
If possible, could you please try to disconnect the powerline devices and the SG105 switch from the network, and connect your phone or computer directly to the AX58, then check if you can get a stable connection and login to its web management page anytime?
As the problem had happened I disconnected everything else and connected via direct wire LAN connection but I still got the same "Operation Failed" when accessing the tplink web GUI - and I get the same reaction if I access tplinkwifi.net or 192.168.0.1 - i.e. the web page is shown but there is no prompt for my password so I cannot login:
I just noticed your point:
If possible, please check if the internet will be stable if you connect a switch between the A1 Telekom modem and the AX58. That is, A1 Telekom modem --- Switch --- AX58.
I have just swapped things around and have now placed the TL-SG105 between the ZYXEL LAN and AX58 WAN connections and I will see if this is a more stable connection.
- Copy Link
- Report Inappropriate Content
@Kevin_Z Hi, so now after 9hrs 40mins the same thing happened again. This means inserting the switch between Zyxel and AX58 had zero impact on the situation. Possibly even made it worse (crashed 1hr earlier than the last crash that I was timing). I wasn't quite sure why this would have any impact but it seemed like the last possible chance.
Any more ideas? Thanks in advance! Or am I going to have to return the AX58 and look for another easymesh router? Can you recommend one?
Please note: I will be on holiday for a week from midnight CEST tonight and so will not respond to any points - please do not close the entry until I return on 1st August.
Cheers!
- Copy Link
- Report Inappropriate Content
@anderigs Got you.
I will escalate your case to our support engineers and they will help analyze it further. Please get back to us via email when you're back.
Happy holidays.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 860
Replies: 14
Voters 0
No one has voted for it yet.