Reply

SRX5308 need to be replaced?

DH
Aspirant
Aspirant

SRX5308 need to be replaced?

My SRX5308 is only about 3 months old. The Primary partition holding firmware v4.3.4-2 was working well since purchase. Then yesterday the router stopped doing VPN. Went back to secondary partition with v4.3.4-1 and VPN worked. Tried to return under warranty and they said to first try a reset. After reset I reflashed firmware v4.3.4-2 and it overwrote v4.3.4-1 and registered as active. [It was a weird flash as it only went to 50% and rebooted.] Now I have v4.3.4-2 on both partitions. Now VPN works, BUT no VPN logs are being generated. Nada. ... I am grateful that VPN is functioning, but why no logs? Using IPsec.

Message 1 of 4
JohnRo
NETGEAR Employee Retired

Re: SRX5308 need to be replaced?

Hello DH, 

 

Welcome to the community! 

 

Did you try refreshing the logs? If so, try dropping the VPN connectivity and then enable it after about 1-2 minutes. See if the logs will show up, if it still doesn't try to refresh it again or reboot the firewall. Have you tested other browsers as well? 

 

Thanks,

JohnRo
NETGEAR® Community Team
Message 2 of 4
DaneA
NETGEAR Moderator

Re: SRX5308 need to be replaced?

@DH,

 

Just following-up on this.  We’d greatly appreciate your feedback.

 

 

Regards,

 

DaneA

NETGEAR Community Team

Message 3 of 4
DH
Aspirant
Aspirant

Re: SRX5308 need to be replaced?

Not sure if solved. Logging seems to come and go as it pleases.  It will log for a few hours, then no logs for days. These machines must be ancient.

Here is what a log looks like now days. Something happens at reboot with time being not right. If we then go in to pretend to change time setting (without changing a thing but clicking save), it will pick up close to correct time, then a short time later gets correct time, then will start logging and connecting with end nodes (until time is right the end nodes don't play nice with it). 

Below is actual log beginning:

Fri Mar 03 14:09:19 2017 (GMT -0600): [SRX5308] [IKE] INFO:  Adding ModeCfg configuration with identifier ...
Tue Feb 28 22:42:08 2017 (GMT +0000): [SRX5308] [IKE] INFO:  clock skew detected, restarting racoon
Tue Feb 28 22:42:08 2017 (GMT +0000): [SRX5308] [IKE] INFO:  clock skew detected, restarting racoon
Tue Feb 28 22:42:08 2017 (GMT +0000): [SRX5308] [IKE] INFO:  clock skew detected, restarting racoon
Tue Feb 28 22:42:08 2017 (GMT +0000): [SRX5308] [IKE] INFO:  clock skew detected, restarting racoon
Sat Jan 01 00:00:11 2000 (GMT +0000): [SRX5308] [IKE] INFO:  IKE started

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 1930 views
  • 0 kudos
  • 3 in conversation
Announcements