Scheduled reboot

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 08:55, 23 June 2012 (edit)
Glenn (Talk | contribs)
(+ Category:Scripts)
← Previous diff
Revision as of 19:22, 16 November 2017 (edit) (undo)
Ian5142 (Talk | contribs)
(What it can be used for)
Next diff →
Line 4: Line 4:
I find that using a scheduled reboot often gives a brilliant transfer and receive rate for wireless which makes a huge difference when in client mode. The higher to the maximum transfer and receive (whilst assuming no other wireless clients are heavily using it such as downloading) I can receive extremely low ping between my primary router and secondary router - around 1-2 ms average with a distance of around 50 metres set in the ACK timer. I find that using a scheduled reboot often gives a brilliant transfer and receive rate for wireless which makes a huge difference when in client mode. The higher to the maximum transfer and receive (whilst assuming no other wireless clients are heavily using it such as downloading) I can receive extremely low ping between my primary router and secondary router - around 1-2 ms average with a distance of around 50 metres set in the ACK timer.
 +
 +It is necessary for WDS to work as intended. When the WDS AP is rebooted, manually or do to power outage, the WDS stations need to reboot in order to reconnect to the WDS AP. Keep Alive, allows this. Just type in the ip of the WDS AP, put in a time of 300 or 1000 s and click apply.
== Not working as intended == == Not working as intended ==

Revision as of 19:22, 16 November 2017

What it can be used for

Scheduled reboot is often used to give the routers a little clearing now and then to keep its performance at its peak. It can also be used in combination with uPnP with the setting "clear ports at startup" enabled to give the benefits of uPnP without the drawbacks of gaps in your security (for long periods of time anyway).

I find that using a scheduled reboot often gives a brilliant transfer and receive rate for wireless which makes a huge difference when in client mode. The higher to the maximum transfer and receive (whilst assuming no other wireless clients are heavily using it such as downloading) I can receive extremely low ping between my primary router and secondary router - around 1-2 ms average with a distance of around 50 metres set in the ACK timer.

It is necessary for WDS to work as intended. When the WDS AP is rebooted, manually or do to power outage, the WDS stations need to reboot in order to reconnect to the WDS AP. Keep Alive, allows this. Just type in the ip of the WDS AP, put in a time of 300 or 1000 s and click apply.

Not working as intended

On DD-WRT v24-sp2 (06/14/11) Build 17201 - I have found that in client mode, scheduled reboot does not work or more so, it only does it for the first time set, despite it being put as "every day." To fix this I used code which a moderator passed onto me and hopefully it works for you too.

  1. Go to DD-WRT configuration page
  2. Disable scheduled reboot in Administration -> Keep Alive
  3. Administration -> Commands
  4. Input
echo "startservice run_rc_shutdown; /sbin/reboot" > /tmp/restart_router
chmod a+x /tmp/restart_router
echo "55 5 * * * root /tmp/restart_router" > /tmp/cron.d/restartrouter
  1. Save startup
  2. You can edit this at any time
  3. I would also recommend giving your router a reboot just to be sure. Administration -> Management should be good enough

The above configuration will then restart every day at 5:55am assuming you have set the NTP correctly. You may also find it useful to find out more information on CRON


Editors note: I have no idea how to fix the numbers whilst giving the code box.