The server is a fixed IP and I currently have a router to router tunnel open for another location.
I think it's stable. It has been running for a long time (almost a year)
the netgear KB article is a derivative of another KB article I tried to follow.
I may be hung up on the whole FQDN - fvs_local.com fvs_remote.com
I'm unable to follow some of the advice (such as leaving the IP blank on policies, that produces an error).
I also see that it says to set the SA life to unspecified which invokes a known issue for Netgear (per their website).
What is key to phase 2 (IKE?) succeeding? This is pretty clearly a phase 2 failure. I'm just mystified as to what goes on in phase 2 that isn't happening.
Main Topics
Browse All Topics





by: RobWillPosted on 2006-11-06 at 20:59:25ID: 17886963
SPD is just the file type ProSafe (SafeNet) uses for it's security policies. If you were to choose to import an existing security policy (ProSafe client configuration) you would see it is an SPD file. Though that may answer your question, I am sure it is of little help. <G>.
m/kb_web_f iles/n1014 36.asp m/casestud y/FVS114/v 11/ casestu dy.html
The ProSafe client is a pain in the neck to set up the first time, but it does work well.
Have you seen the following links ? Though not the same router, the configuration is similar.
http://kbserver.netgear.co
http://www.vpncasestudy.co
If still stuck, perhaps I can help with details.
By the way no need of fixed IP on client, but definitely helps on the Server/FVS124G end.