Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 669 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

NAT rules not working after reboot - SFOS 17.5.10 MR-10

Martin Spanek

Hello,

device: XG210

fw: SFOS 17.5.10 MR-10

problem: 

after reboot , device started about 25 minutes... , after that DNAT not working. Only solution is re-save each rules ...

 

Any idea how to solve it?
 
Thank you
PS: sorry for my english


This thread was automatically locked due to age.
  • 0

    Hi  

    Sorry for the inconvenience caused!

    This is strange behavior, Could you please perform fsck?

    fsck-on-nextboot

    Check the file system integrity of all the partitions. Turning ON this option forcefully checks the file system integrity on the next device reboot. By default, a check is OFF but whenever the device goes in failsafe due to following reasons, this check is automatically turned ON:

    • Unable to start Config/Report/Signature Database

    • Unable to Apply migration

    • Unable to find the deployment mode fsck-on-nextboot[ off | on | show ] Once the check is turned ON, on the boot, all the partitions will be checked. The check will be turned OFF again on the next boot.

    Regards,

    Keyur
    Community Support Engineer | Sophos Support
    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

Cookie Information Banner