Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 68 replies
  • Answers 3 answers
  • Subscribers 54 subscribers
  • Views 13119 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.5 MR1: Feedback and experiences

LuCar Toni

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 



This thread was automatically locked due to age.

Top Replies

  • in reply to twister5800 +4 suggested

    The latest firmware releases removed some alerts, which were in the product. The next alert to be removed is the "Central Managed" alert, which is currently static. All other alerts are removable by "resolving the situation". Deletion/acknolowdiging is something, which requires are complete overhowl of the control center alert system, which is not planned soon. 

    The removal of "XG" is something valid for future releases. Not planned yet. 

    Login notification is currently possible for CFR, if you want to get a report per day of who logged in and when. But not for the "instant notification". This is on the backlog. 

    Jump to answer
Parents
  • 0

    Hi,

    We've got some rbvpn issues since the MR1 update. We've updated the headoffice firewall (XGS3300) to 19.5.1 and we see some problems with icmp/ping traffic from the headoffice to the branchoffice.

    We are using HP Device manager to manage Thin Clients in the remote office and the program can't find the ThinClients anymore since the update. On 19.5 there where no problems. HPDM doe show al local ThinClients.

    Firewall rules are basically Any-Any Allow in both directions. We see no problems from the branchoffice to headoffice, but that is only RDP traffic. 

    Also known clients in the branchoffice do not reply on pings from the headoffice.

    This does not go for all traffic, some devices are available for pings, mostly static devices such as printers.

    Bart van der Horst

    Sophos XG v18(.5) / v19 Certified Architect
    https://www.bpaz.nl

  • 0 in reply to Bart van der Horst

    We think we have solved the problem, customer has windows firewall enabled on major part of the clients and updated the images last week, they are all in private mode now and don't accept ping or any other things from the (trusted) network now. Disabled wfw on one Thin client made them accessible in HPDM.

    Sorry customer didn't inform us on this. And blamed it on the new update we performed.

    Don't know for sure this is the answer, but my money is on it.

    Kind regards,

    Bart van der Horst

    Bart van der Horst

    Sophos XG v18(.5) / v19 Certified Architect
    https://www.bpaz.nl

Reply
  • 0 in reply to Bart van der Horst

    We think we have solved the problem, customer has windows firewall enabled on major part of the clients and updated the images last week, they are all in private mode now and don't accept ping or any other things from the (trusted) network now. Disabled wfw on one Thin client made them accessible in HPDM.

    Sorry customer didn't inform us on this. And blamed it on the new update we performed.

    Don't know for sure this is the answer, but my money is on it.

    Kind regards,

    Bart van der Horst

    Bart van der Horst

    Sophos XG v18(.5) / v19 Certified Architect
    https://www.bpaz.nl

Children
No Data