They listed this as bug 0375204


So with the new build out I gave it a test run and the problem is fix.
v5.4.2-build1151 161213 (GA)

Be advise ipsec is not support in 5.4.2 so you have to unset the ipsec tunnel on the fortigate


Ken
NSE ( network security expert) and Route/Switching Engineer
kfelix -----a----t---- socpuppets ---dot---com
^ ^
=( @ @ )=
o
/ \
No comments:
Post a Comment