This bash script reboots TP-Link routers

TP-Link_TD-W8960N_Reboot.sh

#!/bin/bash

# This software comes without any kind of warranty or license, use it at your own risk.
#
# Author: Andrea Galloni
# E-mail: andreagalloni92[at]gmail{dot}com
#
# Works on TP-Link 300M Wireless N ADSL2+ Modem Router TD-W8960N
# Firmware Version: 1.3.6 Build 100825 Rel.68770n
#

# Parameters setup
username='username'
password='password'
uri_containing_sessionKey='192.168.1.1/resetrouter.html'
baseURI='192.168.1.1/rebootinfo.cgi?'

# takes the sessionKey from the router rebooting web page (192.168.1.1/resetrouter.html)
sessionKey=$(curl -ks --user $username:$password $uri_containing_sessionKey | awk '/sessionKey/{ print substr($3,2,20);exit}')

echo $sessionKey
echo 'REBOOTING'
# performs the get request to reboot the router and flush away the output
curl -ks --user $username:$password $baseURI$sessionKey > /dev/null
echo 'REBOOTED'

TP-Link Reboot Bash Script

AUTHOR: Andrea Galloni (Twitter or Web)

E-Mail: andreagalloni92[at]gmail{dot}com

---

This bash script reboots my TP-Link TD-W8960N router,

first of all it looks for the session key from the administration panel of the router, then, it uses it to reboot the machine.
You can launch it from your Linux host connected from the LAN.

It could work also with other models, but honestly I did not try.

If you have some improvements or suggestions, please create a pull request or write to me at: andreagalloni92{at}gmail[dot]com

Andrea Galloni

does not work, what should I do?

In my case it seems the sessionKey is not always of the same length and the reboot fails.

You might want to update line 19 with something like this:

sessionKey=$(curl -ks --user $username:$password $uri_containing_sessionKey | awk '/sessionKey/{ match($3, /[0-9]+/); print substr($3, RSTART, RLENGTH); exit}')

;-)

Thanks a lot for the contribution @pablen! Is the router the same model?

I think so! The device info page reads:

Firmware Version: 1.4.0 Build 110620 Rel.52053n
Hardware Version: TD-W8960N v3 0x00000002

@Prime-Nobel have you tried using @pablen solution?
PLEASE Lemmie know which was the issue if solved! (maybe it was a credential issue?)

p.s.: I don't have this router anymore, thus I can't test. :S