Hi,
NTP (network time protocol) and WiFi scheduling do not work on my RT-N66U.
The RT-N66U is configured as WiFi-AP (i.e. router disabled), connected to a Cisco cable modem. I configured a port forwarding rule in the Cisco (port 123) to allow NTP traffic to reach the RT-N66U at local LAN IP (fixed IP, 192.168.0.9). Not sure that this is really required, but I think it doesn't hurt.
Internet connection for computers connected to the RT-N66U works fine, no problems at all.
If the RT-N66U is turned on (or at every re-boot), time/date is lost and reset to Jan 1 2011. This seems to be common behaviour, according to information I got through various internet forums. But then NTP should pick the correct time/date - which does not work.
I configured pool.ntp.org as the ntp server (I also tried others, even fixed IP addresses). Even if I hit "Apply" on that page, nothing happens - time/date stays at Jan 1 2011. I also extended the Cisco's port forwarding rule to ALL ports for test purposes - no change.
I can set the time/date through telnet, but this is only a temporary workaround until next re-boot. I really need ntp to schedule WiFi...
Scheduling WiFi does not work also. The time periods I configure through the corresponding web page have no effect, i.e. the WiFi will not turn off at the configured time (time/date set correctly through telnet at this time).
Maybe this is a side effect of the ntp issue, maybe time/date set through telnet is not used for WiFi scheduling - I don't know.
WiFi schedulue DID work a couple of days ago when the RT-N66U was configured as router (at that time I had a different cable modem without routing function). So maybe WiFi scheduling is only an issue when used as WiFi-AP.
Firmware used: 3.0.0.4.270 and 3.0.0.4.260
Any help would be appreciated!
Thanks.
axti
NTP (network time protocol) and WiFi scheduling do not work on my RT-N66U.
The RT-N66U is configured as WiFi-AP (i.e. router disabled), connected to a Cisco cable modem. I configured a port forwarding rule in the Cisco (port 123) to allow NTP traffic to reach the RT-N66U at local LAN IP (fixed IP, 192.168.0.9). Not sure that this is really required, but I think it doesn't hurt.
Internet connection for computers connected to the RT-N66U works fine, no problems at all.
If the RT-N66U is turned on (or at every re-boot), time/date is lost and reset to Jan 1 2011. This seems to be common behaviour, according to information I got through various internet forums. But then NTP should pick the correct time/date - which does not work.
I configured pool.ntp.org as the ntp server (I also tried others, even fixed IP addresses). Even if I hit "Apply" on that page, nothing happens - time/date stays at Jan 1 2011. I also extended the Cisco's port forwarding rule to ALL ports for test purposes - no change.
I can set the time/date through telnet, but this is only a temporary workaround until next re-boot. I really need ntp to schedule WiFi...
Scheduling WiFi does not work also. The time periods I configure through the corresponding web page have no effect, i.e. the WiFi will not turn off at the configured time (time/date set correctly through telnet at this time).
Maybe this is a side effect of the ntp issue, maybe time/date set through telnet is not used for WiFi scheduling - I don't know.
WiFi schedulue DID work a couple of days ago when the RT-N66U was configured as router (at that time I had a different cable modem without routing function). So maybe WiFi scheduling is only an issue when used as WiFi-AP.
Firmware used: 3.0.0.4.270 and 3.0.0.4.260
Any help would be appreciated!
Thanks.
axti