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
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 181 replies
  • Answers 1 answer
  • Subscribers 89 subscribers
  • Views 56737 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: v18.5 MR2: Feedback and experiences

LuCar Toni

https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v18-5-mr2-is-now-available

Release Notes: https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_185_rn.html

"Old" V18.5 MR1 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/128960/sophos-firewall-v18-5-mr1-feedback-and-experiences/

"Old" V18.0 MR5 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/127053/xg-firewall-v18-mr-5-feedback-and-experiences

Please review: https://support.sophos.com/support/s/article/KB-000043489?language=en_US



Prio
[gesperrt von: LuCar Toni um 8:07 AM (GMT -7) am 26 Mar 2022]
Parents
  • 0

    Port Editing Issues with MR2.  After changing 2 separate firewalls to MR-2-Build380 from MR1-1-1-Build365, any form of Interface editing is not allowed.  It give an error "This is a system-reserved interface name".  This occurs with any attempt to save any change of Name, Zone or IP even on an unused interface.

    After some iterative testing, I found that the string "Port" in the name is part of the problem.  Although interfaces have ""Port" there by default, if it's still there on a save it gives that error now.  If the name is changed from say "Port1" to "P1" it saves fine.

Reply
  • 0

    Port Editing Issues with MR2.  After changing 2 separate firewalls to MR-2-Build380 from MR1-1-1-Build365, any form of Interface editing is not allowed.  It give an error "This is a system-reserved interface name".  This occurs with any attempt to save any change of Name, Zone or IP even on an unused interface.

    After some iterative testing, I found that the string "Port" in the name is part of the problem.  Although interfaces have ""Port" there by default, if it's still there on a save it gives that error now.  If the name is changed from say "Port1" to "P1" it saves fine.

Children
No Data
Unfiltered HTML