0;root@Linksys-WRT1900ACS-RB-20: ~root@Linksys-WRT1900ACS-RB-20:~# date
Thu Jan 1 05:17:19 CET 1970
0;root@Linksys-WRT1900ACS-RB-20: ~root@Linksys-WRT1900ACS-RB-20:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
192.168.137.0 * 255.255.255.0 U 0 0 0 br0
0;root@Linksys-WRT1900ACS-RB-20: ~root@Linksys-WRT1900ACS-RB-20:~#
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 6.666/9.918/30.313 ms
0;root@Linksys-WRT1900ACS-RB-20: ~root@Linksys-WRT1900ACS-RB-20:~# ping ntp.midway.ovh
PING ntp.midway.ovh (80.67.184.1): 56 data bytes
64 bytes from 80.67.184.1: seq=0 ttl=56 time=7.639 ms
64 bytes from 80.67.184.1: seq=1 ttl=56 time=7.460 ms
64 bytes from 80.67.184.1: seq=2 ttl=56 time=8.569 ms
64 bytes from 80.67.184.1: seq=3 ttl=56 time=7.376 ms
64 bytes from 80.67.184.1: seq=4 ttl=56 time=7.303 ms
64 bytes from 80.67.184.1: seq=5 ttl=56 time=11.305 ms
64 bytes from 80.67.184.1: seq=6 ttl=56 time=7.188 ms
--- ntp.midway.ovh ping statistics ---
So, date is in 1970 and I am able to ping the NTP server that I have specified in the basic network setup !
But no NTP sync... I am pretty sure that there is no NTP request sent by the router...
To be sure, I have disconnected the router from the internet and I did not get any error massage in the syslog saying that NTP request has failed has we can see in AP mode !
It seems that in "client brigde (routed)" mode, no NTP request is issued !!!
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Mon May 17, 2021 14:09 Post subject:
And the output of ps is? Is ntpclient even running? Was it started on boot? You may need to post appropriately-sized screenshots of the applicable configurations, including wireless. There may be more than to input that gateway address, which may be causing this issue. I seem to recall this when I was tinkering in the past. Check your wireless settings. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon May 17, 2021 14:09 Post subject:
As you were advised, you need to set the static gateway. If I read your last post correctly, your gateway is not specified and therefor the router can't get an update if it doesn't know where to access the Internet.
I run and have been running multiple Routers in this mode for years and never encountered this as long as I set it up correctly with a gateway IP. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
And the output of ps is? Is ntpclient even running? Was it started on boot? You may need to post appropriately-sized screenshots of the applicable configurations, including wireless. There may be more than to input that gateway address, which may be causing this issue. I seem to recall this when I was tinkering in the past. Check your wireless settings.
In the result of the ps commande there is no ntpclient !
As you were advised, you need to set the static gateway. If I read your last post correctly, your gateway is not specified and therefor the router can't get an update if it doesn't know where to access the Internet.
I run and have been running multiple Routers in this mode for years and never encountered this as long as I set it up correctly with a gateway IP.
Even without default gateway (which should be 192.168.137.1), the router is able to access internet: see results of "ping ntp.midway.ovh" above
I tried to use the workaround adding "ntpclient 0.pool.ntp.org" in the startup script.
But then, I get following error message in syslog:
Code:
Jan 1 01:00:25 Linksys-WRT1900ACS-RB-20 daemon.err ntpclient[1645]: Failed connecting to 0.pool.ntp.org [185.254.101.25]: Network unreachable
It is certainly because, in "Client Bridge (Roted)" mode, network configuration takes some time to be up !
So, I have added one cron job to sync to NTP every minute:
Code:
* * * * * root ntpclient 0.pool.ntp.org
And then, after reboot, I can see in syslog that the first sync fails (because of network configuration setup latency as above) but next sync are working !
Code:
Jan 1 01:00:23 Linksys-WRT1900ACS-RB-20 user.info : httpd : http daemon successfully started
Jan 1 01:01:00 Linksys-WRT1900ACS-RB-20 daemon.debug ntpclient[1651]: Connecting to 0.pool.ntp.org [62.210.206.214] ...
Jan 1 01:01:00 Linksys-WRT1900ACS-RB-20 daemon.err ntpclient[1651]: Failed connecting to 0.pool.ntp.org [62.210.206.214]: Network unreachable
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec MLME: auth request, signal -57 (Accepted)
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec IEEE 802.11: authenticated
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec MLME: assoc request, signal -56 (Accepted)
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec IEEE 802.11: associated (aid 1)
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec RADIUS: starting accounting session 978EEE40FF186982
Jan 1 01:01:07 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec WPA: pairwise key handshake completed (RSN)
Jan 1 01:02:00 Linksys-WRT1900ACS-RB-20 daemon.debug ntpclient[1655]: Connecting to 0.pool.ntp.org [129.250.35.250] ...
May 18 08:47:18 Linksys-WRT1900ACS-RB-20 daemon.info ntpclient[1655]: Time set from 0.pool.ntp.org [129.250.35.250].
May 18 08:47:18 Linksys-WRT1900ACS-RB-20 daemon.debug ntpclient[1664]: Connecting to 0.pool.ntp.org [62.210.206.214] ...
May 18 08:47:18 Linksys-WRT1900ACS-RB-20 daemon.info ntpclient[1664]: Time set from 0.pool.ntp.org [62.210.206.214].
May 18 08:47:18 Linksys-WRT1900ACS-RB-20 daemon.info hostapd: wlan1.1: STA 44:85:00:7a:43:ec WPA: group key handshake completed (RSN)
May 18 08:48:00 Linksys-WRT1900ACS-RB-20 daemon.debug ntpclient[1668]: Connecting to 0.pool.ntp.org [51.255.197.148] ...
May 18 08:48:00 Linksys-WRT1900ACS-RB-20 daemon.info ntpclient[1668]: Time set from 0.pool.ntp.org [51.255.197.148].
May 18 08:49:00 Linksys-WRT1900ACS-RB-20 daemon.debug ntpclient[1677]: Connecting to 0.pool.ntp.org [194.177.34.116] ...
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Tue May 18, 2021 16:55 Post subject:
You could've just specified the IP address of the ntp server in the config box, but I can almost guarantee you that there is something missing in your config that is breaking this. I had the same problem on an R9000 until I saw that there was something missing...
I do also get the same issues as of today, with the firm of 26may. If you pay any ip in the basic setup, under the berlin field, it get rejected.
here is :
Code:
Jan 1 01:01:18 ddwc7 daemon.debug ntpclient[1715]: Connecting to 204.93.207.12 [204.93.207.12] ...
Jan 1 01:01:21 ddwc7 daemon.debug ntpclient[1715]: Timed out waiting for 204.93.207.12 [204.93.207.12].
Jan 1 01:01:21 ddwc7 daemon.err process_monitor[1588]: cyclic NTP Update failed (servers 204.93.207.12)
It's a very basic setup, mostly all default, wan in dhcp, no extra service, no dns stuff as dnscrypt look has been removed and can't run via script as the Ntp via ip is not connecting. And that cause issues if you want to connect to a wireguard server, as time is off.
if no ip set in the field, wireguard can connect...
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Thu May 27, 2021 23:44 Post subject:
Please explain what "pay pay any ip in the basic setup, under the berlin field" means. We have no idea of your router or configuration, either. Please include *all* applicable information when you post. Please refer to the forum rules and guidelines. Thank you. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Jun 20, 2021 21:11 Post subject:
Not sure if the NTP problem here has been resolved but I will add a bit of advice just in case it hasn't been tried.
I recently bought a 1900ACS to add to my system as a backup. Although I had a lot of difficulty with installing DD-WRT and finally used an older version (r34311) and ultimately upgraded to the more recent (r46974).
However the NTP would not update. The router is configured as a slave on the LAN for WiFi operations.
After a lot of mucking about I finally realized that I had not changed the the Advanced Routing to Router mode and had not set the Gateway or local DNS. Once I did that the NTP update worked flawlessly.
Ironically before I did fix the above noted, all my WiFi connections to this new router were operating properly. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use