This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.TLR480+ v7 Crashes after 48hrs+
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TLR480+ v7 Crashes after 48hrs+
Region : UnitedKingdom
Model : TL-R480T+
Hardware Version : V7
Firmware Version : 1.0.0 Build 20141208 Rel.36351s
ISP :
Hi,
We are now on our second TL-R480+ router. The first one, a v6, would lockup completely after about 36hrs in production. Lights would be on, but the router could not be pinged either from the LAN or WAN.
TP link replaced this unit with a v7. This worked fine for about 12 days, then displayed the same fault. After power cycling it worked Ok for 3 days, then failed again. Power cycling restores the service in each case. The failure does not coincide with any particular load pattern, it has failed in the middle of the day under relatively high load, but also in the middle of the night when all sites are unoccupied.
Both routers were configured as follows :-
WAN1 (Primary) - PPoE connection for internet access via a WISP provided AP
WAN2 (used for Failover) - DHCP connection to an ADSL router
There are several static routes configured so that traffic for our other sites (8 of) is directed to a third router which is located on the same LAN subnet as the TP-LINK, whilst internet traffic goes to the TP-Link's WAN ports.
There are also port forwards to direct inbound internet traffic to web servers, RDP services etc.
No other configuration changes have been made.
Any suggestions as to why it locks, or how to investigate this? As mentioned when it is in the crashed state it will not respond to pings, so the web interface is inaccessible. If I replace the TL-R480T+ with an ancient Linksys running the DD-WRT firmware the issue disappears, but it's bandwidth is limited and does not support the backup ADSL service.
Thanks for help in advance.
Model : TL-R480T+
Hardware Version : V7
Firmware Version : 1.0.0 Build 20141208 Rel.36351s
ISP :
Hi,
We are now on our second TL-R480+ router. The first one, a v6, would lockup completely after about 36hrs in production. Lights would be on, but the router could not be pinged either from the LAN or WAN.
TP link replaced this unit with a v7. This worked fine for about 12 days, then displayed the same fault. After power cycling it worked Ok for 3 days, then failed again. Power cycling restores the service in each case. The failure does not coincide with any particular load pattern, it has failed in the middle of the day under relatively high load, but also in the middle of the night when all sites are unoccupied.
Both routers were configured as follows :-
WAN1 (Primary) - PPoE connection for internet access via a WISP provided AP
WAN2 (used for Failover) - DHCP connection to an ADSL router
There are several static routes configured so that traffic for our other sites (8 of) is directed to a third router which is located on the same LAN subnet as the TP-LINK, whilst internet traffic goes to the TP-Link's WAN ports.
There are also port forwards to direct inbound internet traffic to web servers, RDP services etc.
No other configuration changes have been made.
Any suggestions as to why it locks, or how to investigate this? As mentioned when it is in the crashed state it will not respond to pings, so the web interface is inaccessible. If I replace the TL-R480T+ with an ancient Linksys running the DD-WRT firmware the issue disappears, but it's bandwidth is limited and does not support the backup ADSL service.
Thanks for help in advance.
Same Problem with V4 .... crashes after every 36hrs
Using the device for 2xWAN bounding.
Additional to this I´m using the DNS updater function.
After every 48 to 36hrs the DNS updater stops working ... (but can still reach www through the device?!)
When trying to reach the device through it´s IP the browser opens the website only half so that no remote reboot is possible (see picture)[already tried from different computers and browsers].
After power recycle everything is ok.
Firmware upgrade does not solve this problem.
IPV6 is deactivated from WAN and LAN side as the support from TP Link already asked this question.
Already bought another device .... same problem!
Additional to this I´m using the DNS updater function.
After every 48 to 36hrs the DNS updater stops working ... (but can still reach www through the device?!)
When trying to reach the device through it´s IP the browser opens the website only half so that no remote reboot is possible (see picture)[already tried from different computers and browsers].
After power recycle everything is ok.
Firmware upgrade does not solve this problem.
IPV6 is deactivated from WAN and LAN side as the support from TP Link already asked this question.
Already bought another device .... same problem!
