Wednesday, February 13, 2013

Software Updates

Here's the latest and greatest.

 FortiOS: 4.0 MR3 Patch 12, Build 656 (Just released)
(stable, recommended for production)

FortiOS: 5.0.1, Build 147
(recommended for limited deployment in production if you need cutting edge features)
at

9 comments:

  1. AnonymousFebruary 14, 2013 at 3:05 AM

    Thanks for that information. Waited for that Patch that much..

    ReplyDelete
  2. AnonymousFebruary 28, 2013 at 6:05 PM

    Just curious, anyone running FortiOS 5.0? How stable is it? Would you recommend running it or should we wait until it's 5.0 MR1 before considering?

    ReplyDelete
  3. SebastianFebruary 28, 2013 at 11:23 PM

    5.0 is pretty much ready for production. 5.0.2 is supposed to be coming out in the next few weeks. I'd start recommending that to my customers.

    ReplyDelete
  4. sashkashurikMarch 2, 2013 at 9:38 PM

    I'm running v5.0,build0147 - it is stable and most bugs we have found are annoying but not critical(Ex.: registered users do not show in the monitoring UI but do show through CLI).

    I would suggest though a clean install instead of upgrade if possible. We had a few performance+ui issues with our unit after upgrade.

    ReplyDelete
  5. albaiteroMarch 27, 2013 at 1:01 PM

    Hi Fellows!

    I installed 5.0.2 but ended up uninstalling it since policies with recurring schedules were not working. Everytime I configured schedules, lost the access tu the internet, regardless of the policy or the schedule.

    ReplyDelete
  6. SebastianMarch 27, 2013 at 1:10 PM

    I tried this on 5.0.2 and could not get it to fail.
    The following debug may give you some clues as to what's going on:

    diag debug reset
    diag debug enable
    diag debug console
    diag debug flow show console enable
    diag debug flow show function-name enable
    diag debug flow filter addr
    diag debug flow trace start 100

    ReplyDelete
  7. AnonymousMay 3, 2013 at 7:38 AM

    I feel 5.0.2 is pretty buggy. A lot of features I've used in the past are no longer working or not available. Granted my firewall still works but I'm rolling back to 4.0 MR3 as soon as our school is out for the summer. Several tickets that I've opened with support have ended with "bug reported" or "I'll have an engineer look at this".

    ReplyDelete
  8. SebastianMay 3, 2013 at 11:14 AM

    Agreed,

    I downgraded to 4.3.12 myself a couple of weeks ago.
    I definitely recommend the latest 4.3.x for production units.

    ReplyDelete
  9. AnonymousMay 18, 2013 at 5:22 AM

    5.0.2 is plenty of bugs.
    In advanced configurations with VPN, failover, it is worse than a Watchguard :)

    FG: please help us out of the hanging sessions!!!!!

    in cases where after a fwall reboot pbx's do not register to eachother anymore due to hanging dead sessions we have lost hours, days of valuable time.

    We stopped planned mass migrations from Watchguard to Fortigate due to BUGS..

    a firmware release has to be tested, and NOT BY CUSTOMERS but by internal CREW :( :( bwah...

    ReplyDelete