balitech wrote

"it is still possible to reboot it using the Telnet interface" please help how to do this? step-by-step please.

Thanks!

Seriously, TP-Link. The fact that we have to go through these lengths to deal with a problem that you refuse to fix is simply unacceptable. Like others have already vowed, this TP-Link purchase will be my last.

Nothing tricky about it. I tried and tested this via a terminal on Debian Linux 8 running on a Raspberry Pi.
[CODE]
$> telnet 10.0.0.1 23 ## this is the firewall IP address
Username:admin
Password: (this will not echo)
TP-LINK > enable ## This goes into privileged mode. My regular password didn't work here, but the default 'admin' did.
TP-LINK > sys reboot
TP-LINK > exit
[/CODE]
I've distilled this into a small expect script. If you're not aware, expect is a versatile tool that lets you automate pretty much anything. In my case I have a cron job setup to ping the firewall every 5 minutes, if pings aren't returned then the script is run. Normally the 'interact' command isn't needed, for whatever reason (which I'm sure somebody will comment on), it is here.
[CODE]
#!/usr/bin/expect
set timeout 20
set name "admin"
set pass "supersecretpassword"
set privpass "admin"


spawn telnet 10.42.1.1 23
expect "Username:"
send "$name\r"
expect "Password:"
send "$pass\r"
send "enable\r"
send "$privpass\r"
send "sys reboot\r"
send "exit\r";
interact
[/CODE]

Gentlemen I have the TL-R470T+ which I bought in Australia 2 months ago. Fortunately I have not experienced this problem you are having. I'm using firmware 1.1.0 Build 20150526 Rel. 71817s. I hope that helps some of you! Love the box but TP-Link is on my no buy list for now!

boward57 wrote

Gentlemen I have the TL-R470T+ which I bought in Australia 2 months ago. Fortunately I have not experienced this problem you are having. I'm using firmware 1.1.0 Build 20150526 Rel. 71817s. I hope that helps some of you! Love the box but TP-Link is on my no buy list for now!

V4
Cheers

Thanks el_segfaulto!

Telnet work perfectly, BUT of course we will hope TP-Link to fixed in next release of it firmware v3 and v4 please!

I am in contact with German support in Germany (yes that exists!) and I have the same issue (TL-R470T+ V4).

I'm testing right now (FW 1.1.0) but it seems to be connected to DynDNS services switched on. Deactivate, reboot and the problem might go away.

I had these problems after 3 days uptime (latest) but now I'm in day 4 and it works!

Will report to TP-Link end of the week - I guess they will be issueing an update. They found the solution with another customer.

TP-Link should read these boards more - they would benefit and not leave users alone for years...

ande wrote

I am in contact with German support in Germany (yes that exists!) and I have the same issue (TL-R470T+ V4).

I'm testing right now (FW 1.1.0) but it seems to be connected to DynDNS services switched on. Deactivate, reboot and the problem might go away.

I had these problems after 3 days uptime (latest) but now I'm in day 4 and it works!

Will report to TP-Link end of the week - I guess they will be issueing an update. They found the solution with another customer.

TP-Link should read these boards more - they would benefit and not leave users alone for years...

Guten tag Ande!

You mean if we disable the dyndns service, it fixes the issue?

Yes, disable DynDNS and Router OK.

After many problems and many emails exchanged with the support I found out this problem because they did not identify the same, the DNS service that causes the error, they said they are already working to correct this.

Yes, for the moment!

TP-Link said they're working on a fix but can't tell when the firmware update will be available. I hope, soon as the problem seems to be solved now.

By the way, do you mean the PARTICULAR service provider that is DynDNS or the entire dynamic DNS service? I was not using DynDNS but I was using no-ip. I have disabled it as well and it has been fine for 19 hours so far (but that's too soon to tell).

It'd be great if you could verify if it's just DynDNS at fault or the entire dynamic DNS service.

Thanks!