Skip to main content
Best answer by cryptochrome

Wow, this release is a true bug fest. I don't even know where to begin.

 

[ul]
  • DNAT Static NAT without port forwarding (e.g. 1:1 NAT) not working, broken
  • Enable a rule with URL Filtering: Firewall doesn't forward traffic for other rules (packets disappear in Nirvana)
  • Rule with URL Filtering set to DENY logs completely unrelated allowed traffic (it logs session close for allowed traffic of other rules)
  • Web Filter log is not working (it logs nothing) - blocked/allowed URLs appear in App Filter log instead[/ul]

     

    Those are just a few things that I noticed. 

    Arent's they ashamed of themselves putting something like that out in the wild? I would be.

    • 1 reply

    bommi
    bommiAuthor
    New Member
    July 27, 2018

    You can now use the packet capture on gui also on small machines without an log-disk!

    The packet capture will use an ram-disk.

    This is the best new feature so far :D

    simonorch
    simonorch
    Explorer
    July 30, 2018

    Very happy indeed to get packet capture back in the gui on the lower end non-disk boxes.

    That one feature has kept some of our customers on 5.2

    SMabille
    SMabille
    New Member
    July 31, 2018

    But not impressed with stability.

    FGT60E, IPS Engine (4.021) keep crashing, massive performance issues (even on rules without UTM).

    Will have to downgrade to 6.0.1.

    Been a long time I haven't been so disappointed by lack of QA so quickly (less than 24 hours) - back to good old buggy Fortinet!

    Terms & ConditionsAccessibility statement