how to stop the vpn daemon

[#1]

Hi, Is there a way to stop the vpn' s daemon on a fortigate 60 only ? I mean, I don' t want to restart my unit entirely. I' m looking in the CLI command now. I' ll post what I' ve found. Thanks. my firmware : Fortigate-60 3.00,build8688,080213

[rwpatterson]

IPSec or SSL?

[UkWizard]

Why on earth would you want to restart the VPN daemon anyway?

[rwpatterson]

When trying to push dynamic web content through the web mode SSL VPN, the system may hang. I' ve had that issue in the past, and my 1000a was down on it' s knees... I had to go into the GUI, disable and re enable the SSL VPN service. to restart the daemon.

[#5]

rwpatterson : it' s VPN IPSEC. I only have VPN ipsec setup on this one. I need that, because only the vpn IPSEC' s feature doesn' t work really good. Two days ago, the vpn link with my HQ office (FGT200A) broke and I can' t understand why. And, when I tried to bring it up, it always stays down. One time, when I bring it up on the FGT60, it says it' s up; but on the FGT200A, it says it' s down. If I' m not clear, say it, please. Thanks for helping me.

[rwpatterson]

Crystal clear. Has this tunnel been in service long, or is it new?

[UkWizard]

The following steps will ' kill off; the IPSec VPN daemon, but how clean this is not certain. So it could very well kill it altogether. From your description of the problem, its sounds like its either misconfigured (compared to the other end) or you have dodgy internet connection somewhere. A reboot of the units is the best bet, but if you really want to risk restarting the daemon, then do the following; # diag sys top -Look for the " ipsecd" process, and note down the Process IP (the number in the next column). - " Control-C" to exit the above command. then # diag sys kill 9 xx -where " xx" is the Process Id you wrote down The ipsecd daemon should restart and when you run " diag sys top" again, it should have a different Process ID this time.

[#8]

rwpatterson: It was firt launch on 2006. And 2 weeks ago, the office' s ISPchange the modem. We just modify a few things on the default GW. but we leave the vpn setup untouched. today, It was up 1 hour and it shut down... ukwizard : i' m going to try what you told me. thanks

[rwpatterson]

Try also from the CLI:

 $ config vpn ipsec phase2
 (phase2) $ edit <interface name>
 (phase2) $ set auto-negotiate enable
 (phase2) $ end
 $

If the tunnel drops, this will attempt to start it up again automatically. Good luck

[UkWizard]

You can also untick the encrypt policy and then tick it again, that resets that VPN connection. Probably a easy thing to try. But if its been working fine until the modem was changed, then its more than likely an issue with the modem or line.