Management Interface (192.168.1.1) not available on VR2800

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

Management Interface (192.168.1.1) not available on VR2800

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Management Interface (192.168.1.1) not available on VR2800
Management Interface (192.168.1.1) not available on VR2800
2020-02-17 15:02:16
Model: Archer VR2800  
Hardware Version: V1
Firmware Version: 0.3.0 0.9.1 v006c.0 Build 170809 Rel.42095n

I have recently started to notice that the management interface for this product fails to work after an undetermined amount of uptime. I usually tend to notice that it has happened by the LEDs not showing on the top panel. The modem/router continues to serve traffic and is connected to my ISP. WIFI and wired connections all work. It just seems to be the management interface that fails.

 

As part of my config, I set the LEDs to switch off between 21:00 and 07:00 each day. When the LEDs are not on during the day, this is a sure-fire indicator that the interface has locked up and I can no longer access it either via TP Link cloud or directly on my network via 192.168.1.1 (both http and telnet).

 

The only way to recover it is to reboot by physically power cycling. This kind of makes the whole 'remote management' thing a bit of a non-starter.

 

Whilst trying to investigate, I've also noticed that I can no longer access the System Log area of the UI. It just displays the white backgroud and no System Log specific text or log entries ever appear. 

 

I had set up a cronjob on one of my internal systems to telnet in and reboot automatically once a week, but that failed last time as the system had hung in the interim. I really don't think I should be required to reboot on a daily basis to ensure continued access to the system.

 

I note there has been no active development of the firmware for nearly 3 years. I find it hard to believe that there have been no security issues identified in that time, let alone bug fixes or general improvements.

 

  0      
  0      
#1
Options