I am trying to get a new ipsec tunnel running towards another vendor
firewall. I get the tunnel up and running, and I can ping the other side
from the CLI in fortigate. But I can't get it from the internal
interfaces I got behind the fortigate. I hav...
I noticed after upgrading mye fortigate 200b to 4.0 mr3 patch 2
(previously I ran the latest mr2 specific fortiap build). I also got the
latest 219 build on the access points. Here is one of the clients
(probably an samsung galaxy s that we got quite...
After upgrading a 200B to 4.0 MR3 patch 2 I can see a strange increase
in cpu and memory usage in cmdbsvr: Run Time: 2 days, 21 hours and 29
minutes 16U, 17S, 67I; 1009T, 398F, 194KF cmdbsvr 29 S 20.8 17.3
proxyworker 54 S 4.8 5.7 ipsengine 60 S < 3....
I got a Fortigate 100A working as a router/firewall for personal users.
We are changing the ISP at the front, and we got all public IP' s. What
I would like to do is to keep the old connection as a backup, as well as
serve the internet connection unt...
Got it running in interface mode now. It seems like there was some
errors in the config on the remote site that tunnel mode didn't catch. I
can't ping the remote subnet from the fortigate, do I need some sort of
default firewall policy to get that ru...
ORIGINAL: Selective one more thing, you dont need to change the port
10443, leave it alone, and do a VIP instead, WAN1 on port 443 -> WAN1 on
port 10443 (and of course choose another IP than the interface IP) What
do you mean with choosing another IP...
I have been running the update I got from Fortinet support for around 4
days now. The CPU usage and memory usage are way better than before, so
it might seem like they have fixed the bug.
I just got a firmware update from fortinet. According to Fortinet the
problem was: Engineering could isolate this bug and fix it. It was
related to an issue with API when trying to save certificate during
wireless renegotiation.
