![]() Up to build r41189 as per this thread:, it was 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. Just type in the ip of the WDS AP, put in a time of 300 or 1000 s and click apply. 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. It is necessary for WDS to work as intended. ![]() 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. 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). Scheduled reboot is often used to give the routers a little clearing now and then to keep its performance at its peak. Jump to: navigation, search What it can be used for
0 Comments
Leave a Reply. |