Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 36 subscribers
  • Views 9298 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

Sophos Firewall: v19.0 MR2: Feedback and experiences

LuCar Toni

Release Post:  Sophos Firewall OS v19.0 MR2 is Now Available 

Old v19.0 MR1 thread:  Sophos Firewall: v19.0 MR1: Feedback and experiences 

https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_190_rn.html

Keep in Mind: V19.5 GA cannot be "downgraded to V19.0 MR2". 



This thread was automatically locked due to age.
  • 0

    Hi "Downgraded" my XG106W from 19.5 GA to 19.0 MR1 and upgraded to 19.0 MR2 ...
    I switched from 19.5 to 19.0 MR1 first... 

    Now i can´t access the firewall through SSH, i get kicked out of console every 4-5 seconds.
    Is there any log, where i can see the reason?

    19.5 GA and 19.0 MR1 had a stable SSH Login ... 

  • 0 in reply to JuergenB

    Yes, under the log viewer > Admin logs !

    Thanks & Regards,
    _______________________________________________________________

    Vivek Jagad | Team Lead, Global Support & Services 


    Sophos Community | Product Documentation | Sophos Techvids | SMS
    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to JuergenB

    BTW: there is a keep alive / timeout value in SFOS for some time:  Configuration of ssh timeout 

    But i am not getting logged out. Check the packet capture on webadmin on port 22. 

    __________________________________________________________________________________________________________________

  • 0

    Upgraded vom V19MR1 to V19MR2 and all https/ssl traffic was blocked due to Application Control. 

    SSL/TLS decryption on Port 80 and 443 is activated.

    We were using a customized App definition filter which is not longer working.

    Then we tried to use the pre defined filter "Block very high Risk (Risk Level5) but traffic was also blocked.

    After using the pre defined filter "Block filter avoidance apps" the traffic was passed.

  • 0 in reply to SG001

    I'd like to investigate, please see DM.

  • +1 in reply to Michael Dunn

    Issue is confirmed, related to Sophos Central pushing templated Application Filter Policy to firewall groups.  Not related to 19.0 MR2.

  • 0

    So we had an interesting experience with an upgrade from 18.5.something to 19.0 MR2 at a customer site earlier this week; when we applied it none of the wifi (APX320, 740s, etc.) clients could connect; in the DHCP log (with the firewall providing DHCP for most of these) we saw constant lease activity on some test devices.  These are all wifi networks provisioned using the separate zone method.  As this needed to be working and in production, we rolled back to the old 18.5 firmware, and function returned.  Didn't have time for a support case, etc. but thank goodness for the rollback function!

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent

    Forgot to mention this was on XG hardware, not XGS.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent

    Ask Sophos about NC-114092 and try this workaround, i received this from sophos

    Workaround 1:

    If you are facing this issue then remove and re-add the affected separate zone SSID from AP/APX.

    Workaround 2:

    If you are facing this issue then restart the awed service. Please note that all the connected AP/APX will be disconnected and connected back.

    service awed:restart -ds nosync

  • 0 in reply to JuergenB

    Interesting, so a known issue.... We'll probably just wait until this is actually fixed.  Is it fixed in the recently released 19.5 MR2?

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Unfiltered HTML