I have this in the startup script of all my routers to send an email when they reboot. I do it more to have accurate time when/if it reboots. I don't have any real need to have proper time on the WiFi bridge. Since it is in the ()& this allows the startup script to continue running anything following while the sleep/ntpclient commands run in the background. This will keep running ntpclient several times every 60 seconds. Since sometimes seems the WiFi bridge can take some time to establish. This is another variation I use on a DDRWT router configured as an Ethernet to WiFi bridge. If the router reboots while i'm not home to deal with it and need to VPN in, then im SOL. Because I run OpenVPN on my router, and OpenVPN is broken without proper time. I have been using a similar workaround to the OP of running ntpclient in the startup script to guarantee that it gets NTP time on bootup. Occasionally it will work but probably 95%+ of the time it doesn't and i've just given up on using the setting in the UI. Doesn't matter if you put an ip or hostname in the GUI field, and also nothing to do with routing/dns resolution because I run my own NTP server based off a GPS receiver at home on my LAN and the router still can't reliably reach it using the UI field specifying the IP of the GPS/NTP device. NTP via the UI has been broken on these WRT1200/1900/3200 routers forever. Pogo - A minimal level of ability is expected and needed.Īt some point, people just get plain tired of this place.īecause they are tired of bottom-feeders and the same old hat. "Life is but a fleeting moment, a vapor that vanishes quickly All is vanity" You can use an IP address, not hostname, in the server address box. If NTP is not working, then there is a dns resolution issue upstream of your router.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |