FVS318N - Clock skew detected

[morris_aiu]

Model: FVS318N

Firmware: 4.3.3-6

Problem:

IPSec tunnel to PFSense router constantly fails and drops internet. Requires hard-reboot for it to come back up.

This is a 4+ times a day thing. This is also happening on 6 of our 28 FVS318N's.

Log from router:

Mon Mar 28 11:31:20 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:31:05 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:30:50 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:30:34 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:30:19 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:30:04 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Should overwrite TID here for NULL data ntry <6
Mon Mar 28 11:22:18 2016(GMT-0600) [FVS318N][Kernel][KERNEL] <sppe_cmd_arp> Fail to delete IPv4 ARP entry <6
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] HTB: quantum of class 11024 is big. Consider r2q change. de_mem_map a03bb000
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] HTB: quantum of class 10001 is big. Consider r2q change.
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 
Mon Mar 28 09:12:23 2016(GMT-0600) [FVS318N][Kernel][KERNEL] Clock skew detected 

Full Log:

FVS318N Full Log 03 - Pastebin.com

Changelog:

Received FVS318N with FWV:4.3.3-2 preloaded.

Hard Reset using 'Reset button' on back of router

Once backup, loaded FWV:4.3.3-6

changed 'admin' password.

added (3) custom services on non-root ports

added (3) port forwards to non-root ports.

added (1) custom NTP server '0.pfsense.pool.ntp.org'

changed NTP mode to 'Sync to NTP Servers on Internet'

checked 'Respond to Ping on Internet Ports' with the suboption 'Any' selected

added (2) IPSec tunnels through wizard

[JohnRo]

Hello morris_aiu, 

Welcome to the community! 

I have seen this error before, it appears that this is caused by the Time Zone not matching thier locations. If you have a box-to-box VPN configured, check each end and make sure that they are on the correct time zone. For FVS318N go to Administration>Time Zone.  

Let me know if this helps. 

Thanks, 

[morris_aiu]

JohnRo,

I've checked all of 6 of our FVS318N's that are having this problem.

They were all showing the correct time, and correct time zone.

Also noticed on a reboot all logs start off in December, until it syncs with NTP servers.

I appreciate the reply!

[JohnRo]

Hello morris_aiu, 

Please try the steps below and see if they will make any changes: 

1. Boot the router and disconnect all established tunnels 
2. Properly sync the time either using NTP servers or manually(using Authoritative Mode). - If the settings are already correct, just click on "Apply"
3. Soft Reboot the Device using option "Reboot the Router" in "Monitoring -> Diagnostics" 
4. After device got booted up, Connect the Tunnels. 
5. Then test the issue. 

If this will not solve the issue, you may have to open a ticket with our support team. 

Thanks, 

[morris_aiu]

---

@JohnRo wrote:

Hello morris_aiu, 

Please try the steps below and see if they will make any changes: 

1. Boot the router and disconnect all established tunnels 
2. Properly sync the time either using NTP servers or manually(using Authoritative Mode). - If the settings are already correct, just click on "Apply"
3. Soft Reboot the Device using option "Reboot the Router" in "Monitoring -> Diagnostics" 
4. After device got booted up, Connect the Tunnels. 
5. Then test the issue. 

If this will not solve the issue, you may have to open a ticket with our support team. 

Thanks, 

---

Hello completed steps 1 through 5 to no avail sadly. Still getting the errors, and IPSec tunnels dropping left and right. After reboot and checking the logs, nothing but the 'Clock Skew Detected' error.

This has now started affecting a few more locations as well.

Any other ideas?

[JohnRo]

Hello morris_aiu, 

I'd contact support if that is the case, it needs to be further investigated to see which one is causing these errors. This probably needs to be looked at by the engineering team and a bug could be created if this is caused by the firmware itself. 

Thanks, 

[just_luc]

Was a solution found to this? I am now having the same issue.

[DaneA]

Hi just_luc,

Welcome to the community! 🙂

So far, there  is no issues log about clock skew in the FVS318N.  Kindly answer the questions below: 

a. Do you have an IPSec VPN tunnel establish between two FVS318N?

b. Were you able to try the troubleshooting steps suggested on this forum thread?  

c. What is the current firmware version of your FVS318N?

Regards,

DaneA

NETGEAR Community Team

[morris_aiu]

Hello just_luc,

regretfully, no solution has been found.

[DaneA]

@morris_aiu,

Were you able to open an online case with NETGEAR Support?  If yes, kindly share what happened. 

Regards,

DaneA

NETGEAR Community Team

[JohnRo]

Hello morris_aiu, 

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved we encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!

Thanks,