Home Network Community > Wi-Fi Routers > connectivity
< Wi-Fi Routers

connectivity

12

connectivity

connectivity
connectivity
Sunday
Tags: #Network Connectivity
Model: Archer AX12  
Hardware Version: V1
Firmware Version: 1.2.1 Build 20250729 Rel. 73566(5553)

After update the latest firmware i am facing some problem in ping request time out through wifi when pinging by using laptop and also in mobile phones sometimes some apps like you tube, instagram are not working properly and after restarting the router everything backs to normal for 2-3 hours and again facing the same issue i am using ofdma and twt with 2ghz and 5ghz on. i changed my router for one day and noticed that there was no problem,it suggests  that this problem not from provider... please help what to do... Through lan there was no problem such that 

  0      
 
  0      
 
#1
Options
13 Reply
Re:connectivity
Monday - last edited Monday

Hello @greninja ,

Welcome to our community.

 

May I know if your network topology diagram is as follows:

ISP modem—router—main deco )))((( client devices

(Note: — stands for wired connection,)))((( stands for wireless connection )

 

Have you changed any settings recently?  If you have enabled the QoS, please disable it for a try.

Please also take screenshots with the ping result and send them here.

 

 

Check Out the Latest Posts: △Pre-release Firmware for Archer AX50 Introduces New Parental Control Features and Enhancements △Pre-release Firmware for Archer AX80 Supports EasyMesh in AP Mode, DoH/DoT, ECO Mode, and More △Introducing AI QoS: Elevate Your Gaming Experience on the Archer GE800 Gaming Router △Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN △Tether KidShield Test Recruitment - Safeguarding Children's Online Experience
  0  
  0  
#2
Options
Re:connectivity
Monday - last edited Tuesday

Isp fiber- onu-routerax12)))(((6 No i did not change any any settings and i disabled Qos... And i will post ping result

  0  
  0  
#3
Options
Re:connectivity
Monday - last edited Monday

  @greninja my ping test in the photograph and i also share my systemlog here in the message

 

####################################################################
#                  Archer AX12 System Log
# Time = 2025-10-13 19:06:50
# H-Ver = 1.0.0 ; S-Ver = 1.2.1 Build 20250729 Rel. 73566
# LAN: I = 192.168.0.1 ; M = 255.255.255.0 ; MAC = E0:D3:62:18:xx:xx 
# WAN: W = static ; I = 192.161.147.xxx ; M = 255.255.255.0 ; MAC = E0:D3:62:18:xx:xx
#      G = 192.161.147.1 ; D1 = 8.8.8.8 ; D2 = 9.9.9.9 
# Clients connected: 6 ; WI-FI : 5 
####################################################################
2025-10-13 18:58:48 led-controller[1799]: <6> 288051 Start to run WAN1_ON
2025-10-13 18:58:48 led-controller[1799]: <6> 288051 Start to run WAN0_OFF
2025-10-13 18:58:48 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 18:58:48 led-controller[1799]: <7> 288009 Failed to read LAN_ON
2025-10-13 18:58:46 led-controller[1799]: <6> 288051 Start to run WAN1_ON
2025-10-13 18:58:46 led-controller[1799]: <6> 288051 Start to run WAN0_OFF
2025-10-13 18:58:46 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 18:58:46 led-controller[1799]: <7> 288009 Failed to read LAN_OFF
2025-10-13 18:58:23 led-controller[1799]: <6> 288051 Start to run WAN1_ON
2025-10-13 18:58:23 led-controller[1799]: <6> 288051 Start to run WAN0_OFF
2025-10-13 18:58:23 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 18:58:23 led-controller[1799]: <7> 288009 Failed to read LAN_ON
2025-10-13 06:03:11 led-controller[1799]: <6> 288051 Start to run WAN1_ON
2025-10-13 06:03:11 led-controller[1799]: <6> 288051 Start to run WAN0_OFF
2025-10-13 06:03:11 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 06:03:11 led-controller[1799]: <7> 288009 Failed to read LAN_OFF
2025-10-13 06:02:39 upnp[11844]: <6> 217505 Service stop
2025-10-13 06:02:32 nat[9187]: <6> 211021 IPSEC ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 L2TP ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 PPTP ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 SIP ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 RTSP ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 H323 ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 TFTP ALG enabled
2025-10-13 06:02:32 nat[9187]: <6> 211021 FTP ALG enabled
2025-10-13 06:02:28 led-controller[1799]: <6> 288051 Start to run WAN1_ON
2025-10-13 06:02:28 led-controller[1799]: <6> 288051 Start to run WAN0_OFF
2025-10-13 06:02:28 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 06:02:28 led-controller[1799]: <7> 288009 Failed to read LAN_OFF
2025-10-13 06:02:27 remote-management[10967]: <6> 282505 Service stop
2025-10-13 06:02:18 led-controller[1799]: <6> 288051 Start to run WAN1_OFF
2025-10-13 06:02:17 led-controller[1799]: <6> 288051 Start to run WAN0_ON
2025-10-13 06:02:17 led-controller[1799]: <3> 288753 Config importing failed
2025-10-13 06:02:17 led-controller[1799]: <7> 288009 Failed to read LAN_OFF
2025-10-13 06:02:16 qos[10350]: <6> 259504 Service start
2025-10-13 06:02:15 qos[10350]: <6> 259503 Function disabled
2025-10-13 06:02:15 qos[10350]: <6> 259505 Service stop
2025-10-13 06:02:08 nat[9187]: <6> 211501 Initialization succeeded
2025-10-13 06:02:07 led-controller[1799]: <6> 288051 Start to run STATUS_ON
2025-10-13 06:02:05 nat[9187]: <6> 211501 Initialization succeeded
2025-10-13 06:02:03 led-controller[1799]: <6> 288051 Start to run GENERAL
2025-07-29 00:01:12 traffic-stats[8984]: <6> 269504 Service start
2025-07-29 00:01:02 factory-reset[8266]: <6> 284504 Service start
2025-07-29 00:00:56 access-control[7712]: <6> 239504 Service start
2025-07-29 00:00:56 access-control[7712]: <6> 239503 Function disabled
2025-07-29 00:00:53 nat[7181]: <7> 211001 Flush conntrack
2025-07-29 00:00:53 nat[7181]: <6> 211502 Function enabled
2025-07-29 00:00:53 nat[7181]: <5> 211051 Create NAT chain succeeded
2025-07-29 00:00:51 nat[7181]: <6> 211501 Initialization succeeded
2025-07-29 00:00:51 nat[7181]: <6> 211501 Initialization succeeded
2025-07-29 00:00:47 basic-security[5462]: <6> 219504 Service start
2025-07-29 00:00:46 basic-security[5462]: <5> 219606 Flush conntrack table succeeded
2025-07-29 00:00:36 firewall[3876]: <6> 209504 Service start
2025-07-29 00:00:22 imb[4115]: <6> 218507 Daemon connection succeeded
2025-07-29 00:00:22 imb[4115]: <6> 218012 ARP Binding disabled
2025-07-29 00:00:22 imb[4115]: <6> 218506 Config interface initialization succeeded
2025-07-29 00:00:22 imb[4115]: <6> 218501 Initialization succeeded
2025-07-29 00:00:20 upnp[3911]: <6> 217505 Service stop
2025-07-29 00:00:18 led-controller[1799]: <6> 288051 Start to run WIFI2G_ON
2025-07-29 00:00:18 led-controller[1799]: <6> 288051 Start to run WIFI5G_ON
2025-07-29 00:00:14 remote-management[3134]: <6> 282505 Service stop
2025-07-29 00:00:00 led-controller[1799]: <6> 288051 Start to run STATUS_SAN
2025-07-29 00:00:00 time-settings[1850]: <6> 279504 Service start
1970-01-01 08:00:18 led-controller[1799]: <6> 288504 Service start
2025-09-24 09:45:00 privacy-assets[19987]: <6> 400030 User Experience Improvement Program set on
 

File:
photo_2025-10-13_19-20-56.jpgDownload
  0  
  0  
#4
Options
Re:connectivity
Monday

  @Joseph-TP 
 

Microsoft Windows [Version 10.0.26100.5074]
(c) Microsoft Corporation. All rights reserved.

C:\Users\subha>ping 192.168.0.1 -n 20

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=28ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=97ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 97ms, Average = 11ms

C:\Users\subha>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=19ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 19ms, Average = 6ms

C:\Users\subha>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=43ms TTL=64
Reply from 192.168.0.1: bytes=32 time=137ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=53ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 137ms, Average = 14ms

C:\Users\subha>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 8ms, Average = 4ms

C:\Users\subha>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=36ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=31ms TTL=64
Reply from 192.168.0.1: bytes=32 time=47ms TTL=64
Reply from 192.168.0.1: bytes=32 time=30ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=28ms TTL=64
Reply from 192.168.0.1: bytes=32 time=47ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=44ms TTL=64
Reply from 192.168.0.1: bytes=32 time=36ms TTL=64
Reply from 192.168.0.1: bytes=32 time=34ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=27ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 47ms, Average = 15ms

ping test from laptop



ping test from desktop- lan connected
Microsoft Windows [Version 10.0.26100.6725]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Surajit>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

i also attach tplink router diagnosis ping test in the web page from router in the picture it is horrible in two band 5ghz and 2.4ghz from laptop
  0  
  0  
#5
Options
Re:connectivity
Tuesday

  @Joseph-TP  i am using auto reboot as i feel it helps and i disabled Qos

  0  
  0  
#6
Options
Re:connectivity
Tuesday

  @Joseph-TP sys log of today 14-10-2025
i connected my desktop lan at 9.04am

and my router auto restart at 6.00am
####################################################################
#                  Archer AX12 System Log
# Time = 2025-10-14 09:13:19
# H-Ver = 1.0.0 ; S-Ver = 1.2.1 Build 20250729 Rel. 73566
# LAN: I = 192.168.0.1 ; M = 255.255.255.0 ; MAC = E0:D3:62:18:xx:xx
# WAN: W = static ; I = 192.161.147.xxx ; M = 255.255.255.0 ; MAC = E0:D3:62:18:xx:xx 
#      G = 192.161.147.1 ; D1 = 8.8.8.8 ; D2 = 9.9.9.9 
# Clients connected: 5 ; WI-FI : 4 
####################################################################
2025-10-14 09:04:55 led-controller[1798]: <6> 288051 Start to run WAN1_ON
2025-10-14 09:04:55 led-controller[1798]: <6> 288051 Start to run WAN0_OFF
2025-10-14 09:04:55 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 09:04:55 led-controller[1798]: <7> 288009 Failed to read LAN_ON
2025-10-14 09:04:53 led-controller[1798]: <6> 288051 Start to run WAN1_ON
2025-10-14 09:04:53 led-controller[1798]: <6> 288051 Start to run WAN0_OFF
2025-10-14 09:04:53 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 09:04:53 led-controller[1798]: <7> 288009 Failed to read LAN_OFF
2025-10-14 09:04:31 led-controller[1798]: <6> 288051 Start to run WAN1_ON
2025-10-14 09:04:31 led-controller[1798]: <6> 288051 Start to run WAN0_OFF
2025-10-14 09:04:31 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 09:04:31 led-controller[1798]: <7> 288009 Failed to read LAN_ON
2025-10-14 06:03:00 led-controller[1798]: <6> 288051 Start to run WAN1_ON
2025-10-14 06:03:00 led-controller[1798]: <6> 288051 Start to run WAN0_OFF
2025-10-14 06:03:00 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 06:03:00 led-controller[1798]: <7> 288009 Failed to read LAN_OFF
2025-10-14 06:02:29 upnp[11675]: <6> 217505 Service stop
2025-10-14 06:02:25 nat[9125]: <6> 211021 IPSEC ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 L2TP ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 PPTP ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 SIP ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 RTSP ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 H323 ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 TFTP ALG enabled
2025-10-14 06:02:25 nat[9125]: <6> 211021 FTP ALG enabled
2025-10-14 06:02:19 remote-management[10924]: <6> 282505 Service stop
2025-10-14 06:02:17 led-controller[1798]: <6> 288051 Start to run WAN1_ON
2025-10-14 06:02:17 led-controller[1798]: <6> 288051 Start to run WAN0_OFF
2025-10-14 06:02:17 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 06:02:17 led-controller[1798]: <7> 288009 Failed to read LAN_OFF
2025-10-14 06:02:12 qos[10272]: <6> 259504 Service start
2025-10-14 06:02:11 qos[10272]: <6> 259503 Function disabled
2025-10-14 06:02:11 qos[10272]: <6> 259505 Service stop
2025-10-14 06:02:06 led-controller[1798]: <6> 288051 Start to run WAN1_OFF
2025-10-14 06:02:06 led-controller[1798]: <6> 288051 Start to run WAN0_ON
2025-10-14 06:02:06 led-controller[1798]: <3> 288753 Config importing failed
2025-10-14 06:02:06 led-controller[1798]: <7> 288009 Failed to read LAN_OFF
2025-10-14 06:02:03 nat[9125]: <6> 211501 Initialization succeeded
2025-10-14 06:01:58 nat[9125]: <6> 211501 Initialization succeeded
2025-10-14 06:01:57 led-controller[1798]: <6> 288051 Start to run STATUS_ON
2025-10-14 06:01:54 led-controller[1798]: <6> 288051 Start to run GENERAL
2025-07-29 00:01:06 traffic-stats[8824]: <6> 269504 Service start
2025-07-29 00:00:59 factory-reset[8219]: <6> 284504 Service start
2025-07-29 00:00:54 access-control[7647]: <6> 239504 Service start
2025-07-29 00:00:54 access-control[7647]: <6> 239503 Function disabled
2025-07-29 00:00:51 nat[7147]: <7> 211001 Flush conntrack
2025-07-29 00:00:51 nat[7147]: <6> 211502 Function enabled
2025-07-29 00:00:51 nat[7147]: <5> 211051 Create NAT chain succeeded
2025-07-29 00:00:50 nat[7147]: <6> 211501 Initialization succeeded
2025-07-29 00:00:49 nat[7147]: <6> 211501 Initialization succeeded
2025-07-29 00:00:46 basic-security[5364]: <6> 219504 Service start
2025-07-29 00:00:46 basic-security[5364]: <5> 219606 Flush conntrack table succeeded
2025-07-29 00:00:35 firewall[3871]: <6> 209504 Service start
2025-07-29 00:00:22 imb[4119]: <6> 218507 Daemon connection succeeded
2025-07-29 00:00:22 imb[4119]: <6> 218012 ARP Binding disabled
2025-07-29 00:00:22 imb[4119]: <6> 218506 Config interface initialization succeeded
2025-07-29 00:00:22 imb[4119]: <6> 218501 Initialization succeeded
2025-07-29 00:00:20 upnp[3914]: <6> 217505 Service stop
2025-07-29 00:00:18 led-controller[1798]: <6> 288051 Start to run WIFI2G_ON
2025-07-29 00:00:18 led-controller[1798]: <6> 288051 Start to run WIFI5G_ON
2025-07-29 00:00:14 remote-management[3127]: <6> 282505 Service stop
2025-07-29 00:00:00 led-controller[1798]: <6> 288051 Start to run STATUS_SAN
2025-07-29 00:00:00 time-settings[1849]: <6> 279504 Service start
1970-01-01 08:00:18 led-controller[1798]: <6> 288504 Service start
2025-09-24 09:45:00 privacy-assets[19987]: <6> 400030 User Experience Improvement Program set on
 

  0  
  0  
#7
Options
Re:connectivity
Tuesday

  @greninja ,

Thank you so much for your reply with details.

The tech team has been made aware of your case; they will likely reach out to you via email to continue troubleshooting. Please check your email inbox and confirm.

Check Out the Latest Posts: △Pre-release Firmware for Archer AX50 Introduces New Parental Control Features and Enhancements △Pre-release Firmware for Archer AX80 Supports EasyMesh in AP Mode, DoH/DoT, ECO Mode, and More △Introducing AI QoS: Elevate Your Gaming Experience on the Archer GE800 Gaming Router △Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN △Tether KidShield Test Recruitment - Safeguarding Children's Online Experience
  0  
  0  
#8
Options
Re:connectivity
Tuesday

  @Joseph-TP sure thank you

  0  
  0  
#9
Options
Re:connectivity
Thursday - last edited Thursday

  @Joseph-TP beta version creating problem in laptops like auto disconnecting and auto no internet

  0  
  0  
#10
Options
Re:connectivity
Thursday

  @Joseph-TP i am showing you a screenshot where you can see that in mobile phone there shown internet but in laptop no internet at the same time i attached bothe file side by side

  0  
  0  
#11
Options
12

Information

Helpful: 0

Views: 201

Replies: 13

Tags

Network Connectivity
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.