Thread Info
  • State Suggested Answer
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 62 replies
  • Answers 2 answers
  • Subscribers 13 subscribers
  • Views 68755 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade to UTM 9.601-5 firmware doesn't start FW NAT rules on boot

Daniel Huhardeaux

Hi,

I got information from my UTM that a new firmware 9.601-5 was available. I installed it and after reboot I discover that all my NAT rules where not activated ! I had to go on each one and disable/enable them to get back the working setup :(

I did it with some of them and then reboot the UTM: again rules where not applied. Disable/enable them and evrything is OK.

For some rules I didn't apply the "automatic firewall rules" in GUI but had create myself the FW rules: those NAT rules where activated. But for NAT rules with forwarding ports to other physical hosts but *not the host himself and the VMs running on it where the UTM lies* doesn't matter which setup (manual or automatically), I have to activate "automatic FW rules" and disable/enable the rules to get them working.

No need to say that prior firmware versions didn't had this problem.

Does anyone face the same problem and confirm?

Daniel



This thread was automatically locked due to age.
Parents
  • 0

    HI Everyone

     

    So glad to see this issue confirmed here - I am NOT going mad after all.  We've had some really big problems with this ; causing us embarrasment and our client's outages

    I can confirm the same activity on a few dozen of my UTMS - I am not sure what UTM firmware version this started with but I've seen it for a month or two at least. After a UTM reboot I need to DISable / ENable the NAT rules to get inbound NAT traffic started again. Not always ALL NAT rules it seems, can be just one rule out of dozens - I am now so scared to update firmware or reboot it's silly,  as I need to try every NAT rule after a reboot and I have so many UTMs to do this on. 

     

    Last post on this thread was Jun 7th - any updates from anyone yet?

     

    Thanks

    Grant AU

  • 0 in reply to GrantAU

    Hi Grant - welcome to the UTM Community!

    You might want to use the trick I outlined in April when this phenomenon first appeared.  If the issue only occurs at reboot, use "@reboot" instead of "0 4 * * *" in the cron jobs.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to DeltaSM

    Firmware version: 9.604-2

    Same issue affecting me, is there any update on this? Please let me know.

    Thanks you

  • 0 in reply to aaa kkk

    Hi,

    just installed 9.605-1 and problems disappears.

    Daniel

  • 0 in reply to Daniel Huhardeaux

    I've also been having this issue for a while (i think it started 9.601, might be earlier, but i'm not sure), assuming it would be fixed in a subsequent update.

    We're now several updates further, and so far 9.605-1 did *not* fix it for me either.

    It's starting to seem kind of silly that after every reboot i have to disable and enable one of my DNAT rules before they all start working...

  • 0 in reply to M1tch

    Hoi M1tch and welcome to the UTM Community!

    Have you tried the trick I suggested earlier in this thread to add a cron job @reboot that disables/enables a DNAT rule?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I have now, it does seem to work!

    This bug might confuse a lot of people, and actually break things meanwhile. It seems silly something like this can drag on for a couple of updates...

  • 0 in reply to M1tch

    Checking in to confirm that the problem still exists for me as well in 9.605-1

  • 0 in reply to BAlfson

    : if guess that the cron job is just is a workaround for now? I mean this is not an official solution? I would like to avoid to do such things on my appliance.

    : did you apply BAlfson solution before updating last firmware? Or was the problem solved by just updating the firmware?

    I will try the new firmware in 10 days and will give you my feedback once it's done.

  • 0 in reply to DeltaSM

    DeltaSM said:


    : did you apply BAlfson solution before updating last firmware? Or was the problem solved by just updating the firmware?

    I didn't apply BAlfson solution, just upgraded and it gone. I will upgrade another UTM this week-end and see if problem disappear too.

    Daniel

  • 0 in reply to DeltaSM

    I don't know if this is in any Sophos KB article or post by a Sophos employee.  I came up with this workaround on my own.

    I note that this issue isn't listed under Bugfixes in the information about 9.605.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to Daniel Huhardeaux

    Daniel Huhardeaux said:

    I didn't apply BAlfson solution, just upgraded and it gone. I will upgrade another UTM this week-end and see if problem disappear too. 

    On another system problem is still existing.

Reply Children
No Data
Unfiltered HTML