The system time zone is different from your local setting.

[ColinTaylor]

restarted through services.msc

What does this mean? services.msc is a Windows application. You were asked to restart NTP on the AP then check its log for errors.

 

[twodose25]

What does this mean? services.msc is a Windows application. You were asked to restart NTP on the AP then check its log for errors.

I don't know how to do that, watched some videos, but didn't work.

 

[bennor]

I don't know how to do that, watched some videos, but didn't work.

How to do so on the router/AP was explained by @dave14305 in post #19 on page one.

Login with ssh and run:

service restart_ntpd

Then check the system log.

 

[twodose25]

no one mentioned how to do it, only to do it.

 

[ColinTaylor]

EDIT: See the next post.

no one mentioned how to do it, only to do it.

Are you using a Windows PC? If so, open a Command Prompt and log into the AP as follows:

ssh [email protected]

Change "admin" to be the AP's login name and "192.168.x.y" to be the IP address of the AP.

Then run the command specified:

service restart_ntpd

Now log into the AP's web interface and check the log (System Log - General Log).

 

[dave14305]

I expect SSH won’t be enabled on the AP if it’s never been used. Alternatively, change the ntp server name on the Administration/ System page in the GUI and hit apply. For example, change pool.ntp.org to us.pool.ntp.org so it will restart the time service in the background.

 

[twodose25]

EDIT: See the next post.


Are you using a Windows PC? If so, open a Command Prompt and log into the AP as follows:

ssh [email protected]

Change "admin" to be the AP's login name and "192.168.x.y" to be the IP address of the AP.

Then run the command specified:

service restart_ntpd

Now log into the AP's web interface and check the log (System Log - General Log

Login with ssh and run:

service restart_ntpd

Then check the system log.

did this, came back done, system time still not correct.

 

[twodose25]

I expect SSH won’t be enabled on the AP if it’s never been used. Alternatively, change the ntp server name on the Administration/ System page in the GUI and hit apply. For example, change pool.ntp.org to us.pool.ntp.org so it will restart the time service in the

I expect SSH won’t be enabled on the AP if it’s never been used. Alternatively, change the ntp server name on the Administration/ System page in the GUI and hit apply. For example, change pool.ntp.org to us.pool.ntp.org so it will restart the time service in the background.

tried this, system time still not correct.

 

[ColinTaylor]

did this, came back done, system time still not correct.

Were there any errors reported from this in the AP's log (System Log - General Log)?

From the AP's SSH session can you confirm that ntp is actually running with the following command:

ps w | grep ntp

and that you can resolve names:

nslookup pool.ntp.org

EDIT: If the above looks OK try running ntp manually in debug mode:

/usr/sbin/ntp -d -n -q -p pool.ntp.org

 

[twodose25]

Were there any errors reported from this in the AP's log (System Log - General Log)?

From the AP's SSH session can you confirm that ntp is actually running with the following command:

ps w | grep ntp

and that you can resolve names:

nslookup pool.ntp.org

16271 AsusAP-U 3324 S grep ntp
32146 AsusAP-U 4000 S /usr/sbin/ntp -t -S /sbin/ntpd_synced -p us.pool.ntp.org

Name: pool.ntp.org
Address 1: 66.118.231.14 time4.lshiy.com
Address 2: 45.79.82.45 ntp.sfo.icanbwell.com
Address 3: 50.117.3.95
Address 4: 5.78.62.36 static.36.62.78.5.clients.your-server.de

don't see any errors in the system log.

 

[ColinTaylor]

16271 AsusAP-U 3324 S grep ntp
32146 AsusAP-U 4000 S /usr/sbin/ntp -t -S /sbin/ntpd_synced -p us.pool.ntp.org

Name: pool.ntp.org
Address 1: 66.118.231.14 time4.lshiy.com
Address 2: 45.79.82.45 ntp.sfo.icanbwell.com
Address 3: 50.117.3.95
Address 4: 5.78.62.36 static.36.62.78.5.clients.your-server.de

That all looks normal. Can you try the command I added to my previous post. Here it is again:

/usr/sbin/ntp -d -n -q -p pool.ntp.org

 

[twodose25]

That all looks normal. Can you try the command I added to my previous post. Here it is again:

/usr/sbin/ntp -d -n -q -p pool.ntp.org

ntp: 'pool.ntp.org' is 168.235.69.132
ntp: sending query to 168.235.69.132
ntp: send failed: Network is unreachable
Alarm clock

 

[dave14305]

Did you set a gateway on the AP when configuring the static address?

 

[ColinTaylor]

ntp: 'pool.ntp.org' is 168.235.69.132
ntp: sending query to 168.235.69.132
ntp: send failed: Network is unreachable
Alarm clock

That's very strange.

As per Dave's post, what is the output of:

netstat -rn

Do you have any kind of IP blocker running on your main router, like Skynet?

P.S. Are you running stock Asus firmware or Merlin's?

 

[twodose25]

That's very strange.

As per Dave's post, what is the output of:

netstat -rn

Do you have any kind of IP blocker running on your main router, like Skynet? < no

P.S. Are you running stock Asus firmware or Merlin's? < merlin

 

[dave14305]

@twodose25 Did you set the Default Gateway to be the router IP (same as DNS Server1)?

 

[twodose25]

@twodose25 Did you set the Default Gateway to be the router IP (same as DNS Server1)?

yes the default gateway is the routers ip.

 

[ColinTaylor]

yes the default gateway is the routers ip.

Sounds like it might be a bug then.

Can you SSH into the AP and post the output of this command:

netstat -rn

 

[twodose25]

Sounds like it might be a bug then.

Can you SSH into the AP and post the output of this command:

netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0

 

[ColinTaylor]

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 br0

Thanks for that. It does seem to confirm that you're missing the default route.

Can you check whether it has been set correctly in NVRAM using this command:

nvram get lan_gateway

It should return 192.168.1.1

If you're still using a static IP address on the AP it should look something like this:

Alternatively, just set it to get the information automatically for both the LAN IP and DNS Server.

You can set the gateway manually using the following command. However, it won't survive a reboot.

route add default gw 192.168.1.1 br0