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

Sophos Firewall: v19.5 MR1: Feedback and experiences

Release Post:   Sophos Firewall OS v19.5 MR1 is Now Available 

The old V19.5 GA Thread:  Sophos Firewall: v19.5 GA: Feedback and experiences 



Removed Prio.
[gesperrt von: LuCar Toni um 11:37 AM (GMT -7) am 9 May 2023]
Parents
  • Hello,

    very bad experience for me.
    I upgraded from 19.0.1 to 19.5.1
    After the update, user authentication works poorly, and they have to restart their PC.
    I lost all "ClientLess User" access
    Even when recreating by hand, the firewall does not allow flows to pass.

    I had to revert to 19.0.1, then update to 19.0.2.
    And there, everything works perfectly.

    I can only advise against version 19.5.1 :(

  • Hello  ,
    Have you notice any specific error during clientless user recreation?
    If possible, then please PM me appliance access detail so I can debug further.

    Thanks

  • Hello Bhavik24,

    Sorry, but everything was erased due to firmware rollback.
    I had opened a case with SOPHOS, but it was closed following my switch to 19.0.2

    FYI, when I booted to firmware 19.5.1, absolutely no clientless users appeared in the list of active users (under current activities -> live users).

    After returning to 19.0.1, everything appears again.
    After migration to 19.0.2, everything also appears correctly.

  • There can be (unrelated to the firmware version) issues with the services, providing the clientless users.

    Most likely, if this is the case, it is a one time issue: 

    Restarting the Authentication daemon fixes this and it should not come up again. 

    __________________________________________________________________________________________________________________

Reply
  • There can be (unrelated to the firmware version) issues with the services, providing the clientless users.

    Most likely, if this is the case, it is a one time issue: 

    Restarting the Authentication daemon fixes this and it should not come up again. 

    __________________________________________________________________________________________________________________

Children