Sophos Firewall: v21.0 EAP1: Feedback and experiences (EAP Thread)

Release Post:  Sophos Firewall v21 Early Access Announcement 

Whats New Link: https://assets.sophos.com/X24WTUEQ/at/7t8k46h9ttmxt6pn8g58k7wb/sophos-firewall-key-new-features-v21.pdf 

Please provide feedback using the option at the top of every screen in your Sophos Firewall as shown below or via the Community Forums.

NOTE: Sophos Firewall v21 does NOT include support for XG and SG Series appliances. XG Series EOL is March 31, 2025.
XG/SG Hardware will find them self until the EOL on the V20.0 Branche with MR2 + 
Sophos SFOS Home users are not affected, as SFOS Home is running the software version. 

For LE Related config issues, please review this post first:  Let´s Encrypt Deep Dive & Debugging in SFOSv21.0  



LE
[bearbeitet von: LuCar Toni um 8:59 AM (GMT -7) am 31 Aug 2024]
Parents
  • UPDATE 30/8-2024: SOLVED - NOT A BUG - BUT MY ISP WHO CHANGED IP AFTER REBOOT :-)

    IPSEC issues

    have Tunnel interfaces with IKEv2, thoose cannot establish anymore.

    Just seeing this on the GUI, have not looked into the CLI logs yet:

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v20 Technician

  • Hi Martin,

    Can you check if you are facing issue due to below known NC?

    Sophos firewall running on 20.0.MR1 or above, IPsec site-to-site tunnel bring up with default IKEv2 profile may have issues in some conditions, where SFOS keeps re-attempting the connection with the peer IPsec gateway (SFOS or 3rd party device) but the tunnel will not come up.

    Cause:

    This is because SFOS running with 20.0.MR1 or above, with the default IKEv2 profile of IPsec tunnels, increases the IKEv2 packet size beyond 1500 bytes causing fragmentation.

    If such fragmented packets are not handled or dropped in the network due to PMTU issues will result in S2S IPsec tunnel bringup issue.

    In 20.0.MR1, Strongman and OpenVPN versions are upgraded, adds more default fields to the IKEv2 packet and increases the packet size.

    Workaround:
    In the IPsec profile, reduce the number of DH groups to minimum of 4 (default IKEv2 has 6) or keep the exact DH group that is being used on the far end IPsec gateway.

    -Alok

Reply
  • Hi Martin,

    Can you check if you are facing issue due to below known NC?

    Sophos firewall running on 20.0.MR1 or above, IPsec site-to-site tunnel bring up with default IKEv2 profile may have issues in some conditions, where SFOS keeps re-attempting the connection with the peer IPsec gateway (SFOS or 3rd party device) but the tunnel will not come up.

    Cause:

    This is because SFOS running with 20.0.MR1 or above, with the default IKEv2 profile of IPsec tunnels, increases the IKEv2 packet size beyond 1500 bytes causing fragmentation.

    If such fragmented packets are not handled or dropped in the network due to PMTU issues will result in S2S IPsec tunnel bringup issue.

    In 20.0.MR1, Strongman and OpenVPN versions are upgraded, adds more default fields to the IKEv2 packet and increases the packet size.

    Workaround:
    In the IPsec profile, reduce the number of DH groups to minimum of 4 (default IKEv2 has 6) or keep the exact DH group that is being used on the far end IPsec gateway.

    -Alok

Children
No Data