On Thu, Oct 1, 2009 at 4:59 PM, Alex Hewitt <hewitt_t...@comcast.net> wrote: > If the router doesn't know the time .. then the VPN > connection might not work.
Quite possible. If it's using X.509 certificates (like SSL does), one can specify effective and expiration dates in the certificate. If they are set, and the LinkSys box is checking them, having the wrong time will likely cause it to conclude its certificate is invalid. Any idea what protocols the LinkSys is using? IPsec? IKE? SSL/TLS? X.509? > Does anyone have any ideas? (1) Check for a firmware update. (2) Look for a way to set the clock manually (no time server). (3) Set up a DHCP reservation on the WAN side for the LinkSys box, and give an NTP server in the DHCP options, in the hope that time is actually the problem, and the LinkSys box will listen. Beyond that, you're at the mercy of the vendor. Which leads me to: (4) I've never heard anything good about SOHO+VPN scenarios. Which in turn leads me to: (4)(a) Throw out the SOHO crap and buy a real VPN appliance. (4)(b) Grab a couple PCs, install Linux and OpenVPN, and use that. Again: SOHO stuff has its uses. I had a LinkSys router+WAP+switch at home, and was happy with it. Their products are appropriate for home use, and I recommend them for that. If you're running a real business on them, you're crazy. :) -- Ben _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
