NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FVS318N - Clock skew detected
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 ...
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!
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,
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?
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,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
