Router unresponsive after some time, requires manual reboot

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Router unresponsive after some time, requires manual reboot

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Router unresponsive after some time, requires manual reboot
Router unresponsive after some time, requires manual reboot
2021-07-08 18:55:03 - last edited 2021-07-09 11:54:14
Model: TL-MR6400  
Hardware Version: V5
Firmware Version: 1.1.0 0.9.1 v0001.0 Build 201207 Rel.56223n

My TL-MR6400 randomly stops responding (as in, it's unreachable via WiFi or Ethernet).

 

I've tried everything I know and I'm unable to debug further! Any help/pointers would be greatly appreciated :)

 

Hardware Version:‪ TL-MR6400 v5 00000001

 

My current network is composed of:

- TL-MR6400 4G Router

- 3 Devolo Powerline adapters scattered around the house

- 1 Raspberry Pi server, streaming video camera to cloud

- 1 IP Camera (Reolink E1, if you must know)

- Usual clients (currently I've been alone, so… a MacBook, an iPhone, and an Apple Watch).

 

The router had been functioning properly until July 6th, until I've set up the Raspberry to stream continuously to the cloud (~400kbps bitrate) on July 6th. The first time I had the problem was on July 7th morning. Since then I have had to restart it 4 times manually.

 

I noticed I wasn't using the latest firmware. Updated it and the problem persists.

 

I'm able to get packets through my home network (via Powerline), but any attempt to ping the router results in a timeout:

 

PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0

 

There is no information in the System Log.

 

Router lights are all on (during normal operation, or when the problem happens).

 

The Router has a pretty standard configuration. The non-defaults include:

- Dynamic DNS (using tplinkdns.com)

- Virtual Servers / NAT Forwarding (HTTP and SSH)

- Some reserved IP addresses (Raspberry and IoT stuff)

  0      
  0      
#1
Options
1 Reply
Router unresponsive after some time, requires manual reboot
2021-07-17 08:39:10

The main issue was the ethernet cable malfunctioning between the router and the mesh network.

Replacing that cable solves the connectivity issues.

 

I'm an idiot.

  0  
  0  
#2
Options