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
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 49 subscribers
  • Views 12656 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.
Parents
  • 0

    Hi,

    since we upgraded from 19.0.1 MR1 to 19.0.2 MR2 in the firewall rules the object "##ALL_IPSEC_RW" is not hitted anymore.
    So we have to edit all firewall rules for our homeoffice users connecting via sophos connect client.

    I thought, using this objects is recommended instead of using network objects?

    Is this a general problem? Or i am the only one having this problem as everytime i have a problem?

Reply
  • 0

    Hi,

    since we upgraded from 19.0.1 MR1 to 19.0.2 MR2 in the firewall rules the object "##ALL_IPSEC_RW" is not hitted anymore.
    So we have to edit all firewall rules for our homeoffice users connecting via sophos connect client.

    I thought, using this objects is recommended instead of using network objects?

    Is this a general problem? Or i am the only one having this problem as everytime i have a problem?

Children
  • 0 in reply to Nafets

    Update: It seems like the first leased IP-Address from connect client range is not included in ##ALL_IPSEC_RW ... ?! wtf.
    All other connected users have no problems. only the guy with the first ip...

    Configured range:

    User with IP 172.27.72.10 has problems.

    Policy Tester:

    Second IP of Lease:

    I have now done a quick and dirty workaround: I created a dummy vpn user and assigned a static ipsec remote address... so the first range ip is never leased...

    @ SOPHOS: Please check this scenario if this is a general problem in 19.0.2-MR2

    EDIT: Please also check ##ALL_SSLVPN_RW too...

Unfiltered HTML