Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 99 replies
  • Answers 2 answers
  • Subscribers 65 subscribers
  • Views 22433 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 GA: Feedback and experiences

LuCar Toni

https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-os-v19-is-now-available

Release Notes: docs.sophos.com/.../index.html

"Old" V18.5 MR3 Thread: https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v18-5-mr3-is-now-available

The V19.0 EAP Community: https://community.sophos.com/sophos-xg-firewall/sfos-v19-early-access-program/

About the Upgrade Issues: 

See Known Issue List in Release Note

s: 



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

    Picking up issues with NAT. I have multiple public IP's configured on a singe port all using the same Gateway which is the ISP's router. I need some outgoing traffic to come from a specific IP configure on the port.

    For this I used NAT rules and translated the source to the IP specific public IP address I want the traffic to come from. Since v19, traffic is now translated to the IP of my ISP's router, in other words, the gateway for the port.

  • 0 in reply to Riaan

    Sorry for the late reply. NAT issues have been on going for a long time in SFOS. I reported this back in the V16 days, but they never did anything about it. Every once in a while on upgrades of a few different clusters, some NAT rules would just stop processing. If you had custom NAT rules, the easiest fix is to just delete them, and recreate. I also specify interfaces in NAT rules and disable the default SNAT rule. It seems to help on upgrades.

Reply
  • 0 in reply to Riaan

    Sorry for the late reply. NAT issues have been on going for a long time in SFOS. I reported this back in the V16 days, but they never did anything about it. Every once in a while on upgrades of a few different clusters, some NAT rules would just stop processing. If you had custom NAT rules, the easiest fix is to just delete them, and recreate. I also specify interfaces in NAT rules and disable the default SNAT rule. It seems to help on upgrades.

Children
No Data
Unfiltered HTML