Hear, hear... There are some large issues that have been allowed to make it through to the GA releases. That is a shame. I really enjoy promoting Fortigate firewalls wherever I can. But, it is not easy to do so when there are obvious bugs in the FortiOS. I give them the old " Fortinet is a young growing company" speech. But I grow tired of making that statement. The trouble isn' t just with new customers. The existing customer base is scared to upgrade, even to the latest Maintenance Release, for fear of losing configuration or even worse: losing functionality. That is a terrible thing. Stability and consistency should rank highly with a developer of security products. Quality assurance is a must, if people are to depend on this company for network protection. Fortinet has a fine product on their hands. I really hope they continue to improve/refine their development process.
I agree, I like the product but I wouldn' t dare upgrade it at this point in time as right now it works the way I need it to. But using the excuse they are a young company just isn' t valid if you are out to make a good impression on the people you are trying to convice to use your product. Small bugs are one thing promoting functions that just do not work is bad business practices, so is fixing them with in one release then breaking them again in the next. QA, Technical support, and product development need to work a little more closely together, I guess it' s possible that it' s the PM' s fault making them push something out that just isn' t up to par, either that or version control just doesn' t exist here. I guess that is the end of this rant (for now)
I agree also, this seems to really be the only major gripe about the product. Small bugs we can live with (like spelling mistakes ) but not the major memory leaks.
Same problems with Cisco - We' ve had nightmares with VPN recently brought about by minor upgrades in code. It' s not a little company thing, but at least they have the excuse that they are actually constantly developing functionality following feature requests etc You won' t get any great joy in a hurry from submitting a feature request to Cisco. If you stay with the rule " If it ain' t broke, don' t fix it" and stay just a bit behind the bleeding edge I don' t think that' s too bad.
The problem with that is, it would seem more of a marketing push to get all of this new code out rather then fix the current issues, I mean if people were to read this forum before ever buying the product I would have to say that 8 out of 10 would more then likely not purchase a fortinet product. Don' t get me wrong all companies have their bugs (bad thing) but to not fix one version before moving onto the next is just bad practice. I like the product thank god the features I need aren' t one of the broken ones, well other then the stupid wireless tunneling issues. Cisco has been great with the dealings I have had with them, they do their part as far as supporting their product, and releasing fixes and patches
From now on after what though? After MR4, MR5, MR6? I know they' ve made changes to the soon to be released MR4. See my big post here: http://support.fortinet.com/forum/tm.asp?m=3989
way too much missinformation being passed onto the consumers by people who don' t make the decisions (tech support) not saying you guys arent informed i am sure a million times better then i and probably even people taking support calls, we need someone with a real inside to find out what the deal really is