Logic fault in the Access Schedule setup and a feature request
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Logic fault in the Access Schedule setup and a feature request
Region : Others
Model : TL-MR3420
Hardware Version : V2
Firmware Version : 3.13.27 Build 121206 Rel.60215n
ISP : CellC
There appears to be a logic error in the setup of the access scheduler. The start time cannot be higher than the end time, so how do you schedule for the hosts to be denied access from 22h00 at night until 06h00 the next morning?
Also, it would be so much simpler to select a host by MAC address in a table format like the DHCP Client List, and simply enter on and off times there. The current method is unnecessarily complicated.
While we're redesigning this, can you apply a data quantity limit per host as well? I've a couple of users who unintentionally exceed their daily limits and this would be a simple way to fix that. It would probably make TP-Link one of the few router manufacturers offering this useful feature if you can do it.
Thanks in advance
Model : TL-MR3420
Hardware Version : V2
Firmware Version : 3.13.27 Build 121206 Rel.60215n
ISP : CellC
There appears to be a logic error in the setup of the access scheduler. The start time cannot be higher than the end time, so how do you schedule for the hosts to be denied access from 22h00 at night until 06h00 the next morning?
Also, it would be so much simpler to select a host by MAC address in a table format like the DHCP Client List, and simply enter on and off times there. The current method is unnecessarily complicated.
While we're redesigning this, can you apply a data quantity limit per host as well? I've a couple of users who unintentionally exceed their daily limits and this would be a simple way to fix that. It would probably make TP-Link one of the few router manufacturers offering this useful feature if you can do it.
Thanks in advance