Linux, FreeBSD, Juniper, Cisco / Network security articles and troubleshooting guides

It is currently Tue Dec 07, 2021 5:29 am

Message body:
Enter your message here, it may contain no more than 60000 characters. 

:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
Font size:
Font colour
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation code
Confirmation code:
In an effort to prevent automatic submissions, we require that you enter both of the words displayed into the text field underneath.

Topic review - Site2Site Ipsec/Dialup/ike v2
Author Message
Post subject: Site2Site Ipsec/Dialup/ike v2  |  Post Posted: Wed Sep 16, 2015 9:07 am
I have gotten a couple of requierments from the infrastructure architects at my job, for the site2site vpn to our small offices.

- Cert authentication
- Ike V2

There are some offices that have a dynamic ip, when i did some googling i found this two articels that seems to contradict eachother. ... login=true here they are using aggressive mode (so i guess it wont work in ike v2) ... ec-site-... here it also says that i have to use aggresive mode vpn. ... id=KB24704 here they solve it in a different way (i guess this solution supports ike v2? )

So can i solve it with in this way?

gateway gw_svr {
ike-policy ike_pol_svr;
dynamic {
distinguished-name {
container CN=client-srx;

Like in the pki example.
Jump to:  
cronNews News Site map Site map SitemapIndex SitemapIndex RSS Feed RSS Feed Channel list Channel list

Delete all board cookies | The team | All times are UTC - 5 hours [ DST ]