Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 99 replies
  • Answers 2 answers
  • Subscribers 78 subscribers
  • Views 41485 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

    We are facing an issue due a rollout of an XGS4500 v19 GA Cluster these days. We set al lot of static routes (around 40) through the GUI. After goLive we figured out that around 30% of the routes in the GUI are not avaliable on the backend. These routes are shown in gui, but never in the cli "ip route". It picks up randomly routes, so it have nothing to do with the order when you put them in.

    We have tested to boot the primary and then the aux device, without any change in the situation.

    After we figured out the packets are leaving on the WAN interface instead of the ifc where they should go, we found a workaround. (we followed relayed dhcp traffic)

    -> Just reopen the non deployed routes and click simply save again -> the will appear in the routing table a moment later.

    Due this is reall weird, we opened a case 05295087 and will see what is the reason.

    This might be helpful for all of you, to doublecheck the entered & the real applied routes on the CLI to avoid our problem ;)

Reply
  • 0

    We are facing an issue due a rollout of an XGS4500 v19 GA Cluster these days. We set al lot of static routes (around 40) through the GUI. After goLive we figured out that around 30% of the routes in the GUI are not avaliable on the backend. These routes are shown in gui, but never in the cli "ip route". It picks up randomly routes, so it have nothing to do with the order when you put them in.

    We have tested to boot the primary and then the aux device, without any change in the situation.

    After we figured out the packets are leaving on the WAN interface instead of the ifc where they should go, we found a workaround. (we followed relayed dhcp traffic)

    -> Just reopen the non deployed routes and click simply save again -> the will appear in the routing table a moment later.

    Due this is reall weird, we opened a case 05295087 and will see what is the reason.

    This might be helpful for all of you, to doublecheck the entered & the real applied routes on the CLI to avoid our problem ;)

Children
No Data
Unfiltered HTML