Timeline for Fortinet 60D acting as IPSec VPN Client?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 1, 2015 at 23:44 | comment | added | Kyle Brandt | Thanks I'll go the CLI route. My background is Cisco, but part of getting this particular device was to get comfortable with foritinet since we are moving from some of our asas to foritinet. | |
| Aug 1, 2015 at 23:40 | comment | added | user1016274 | If you've used CLI before then I'd recommend doing the setup in CLI only. Be sure to use "set modconfig ena" in phase1. And I'd try site-2-site to Cisco via assistant as well - you can always restrict access via the policy. | |
| Aug 1, 2015 at 23:35 | comment | added | Kyle Brandt | Thank you, I'm at 5.2 but at least I know it is possible. This is for getting my home Fortinet 60D connected our colo, so not all my work devices need to have the VPN on. I'll update with how it goes. Tried a couple things, but deleting VPN configs the GUI is pain in the butt (maybe not possible, had to use CLI to kill some refs - the phase-interfaces) so wanted more direction since iterating was slow. | |
| Aug 1, 2015 at 23:08 | history | answered | user1016274 | CC BY-SA 3.0 |