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

Release of v17 MR-2?

Hej,

now that MR-1 has appeared, I wanted to ask when MR-2 will appear? The problems and instabilities of IPSec in v17 (especially in connection with V16.5) are very annoying.



This thread was automatically locked due to age.
Parents
  • Hi everyone,

    MR-2 release is tentatively on December 5th. This can change with unforeseen circumstance, but we'll update this thread if that is the case.

    We'll also post a Discussion post with Release Notes on the Community once its live.

    Cheers,
    Karlos

  • Can anyone confirm if country blocking is now working properly?  This was promised in GA, then MR-1, then MR-2 and I don't see it on the release notes unless I'm missing it somewhere.  Thanks.

  • See my comment above about custom IPSEC policies.  It appears that custom ipsec policies are not showing up as selectable.  If you go to modify that VPN connection you will not be able to select your IKEv2_KeyNegTries_Unlimited Policy I'm betting (it wont be in list)

  • If this is what you mean, it's there ...

     

  • I repeat to anyone with a VPN.  DON'T INSTALL v17 MR2

    Back to MR-1.  VPN is back to work.

    With Sophos, I have reverted back so many times (on many of their products) I can now "moon walk" better than Michael Jackson.  Note to Sophos Quality Control: Call me before you release anything.  

    Like I have written before ... I suggest everyone to skip v17 MRx, skip v18, skip v19, and wait for Release v20  ...

    Update:  Reconstructing all VPNs from made them work again.

  • I just upgraded to MR-2 and my SSL VPN (Remote Access) is working. I have a very basic setup though for home use.

  • hi again,

    after installing V17 mr2 i can confirm there are big big issues with pppoe connection (connexion are for ever "connecting in the network status but pppoe connexion esatblished in log viewer) and ipsec vpn (same as v17 GA and MR1, vpn never came up !!!!

    2 bascical things runing fine in v16.5 mr8 are now almost dead.

    this is really painful !!!!

  • Our remote VPNs work.  It's the main VPN between both main offices that failed.  Our VPN is very basic too.  Is asking for IKEv2 too much ?

    By the way, when testing MR2, I have rebooted twice both main firewalls.  VPN would never reconnect.  I had these two errors (many times):

    2017-12-06 12:48:54SYSTEMmessageid="18057" log_type="Event" log_component="IPSec" log_subtype="System" status="Expire" user="" con_name="" con_type="0" src_ip="" gw_ip="" local_network="" dst_ip="" remote_network="" additional_information="" message="IKE_SA timed out before it could be established"

    2017-12-06 12:42:58SYSTEMmessageid="18046" log_type="Event" log_component="IPSec" log_subtype="System" status="Deny Session" user="" con_name="" con_type="0" src_ip="" gw_ip="" local_network="" dst_ip="" remote_network="" additional_information="" message="creating local authentication data failed"

    Update:  Reconstructing all VPNs from scratch made them work again.

  • Hi Scott,

    Scott_D_L said:
    See my comment above about custom IPSEC policies.  It appears that custom ipsec policies are not showing up as selectable.  If you go to modify that VPN connection you will not be able to select your IKEv2_KeyNegTries_Unlimited Policy I'm betting (it wont be in list)

    The policies shown in this dropdown are dependent on several factors. There is already a ticket open to improve the situation, because it is not obvious which policies can be expected in the list. It depends on Gatewaytype (initiator/responder) as well as options in the policy, mainly 'When Peer Unreachable' setting.

    You have a sophos support ticket open regarding this issue, may i ask you for the ticket number?

    Kind Regards,

    Afschin

  • Thanks Afschin,

     

    Case ID# is Case 7778728  .  I'm on another call at the moment, but feel free to use the access ID I gave in ticket to take a look. (this is system is in production, so please be aware of that )

     

    Thanks for your help!

     

    -Scott

  • Hello Big_Buck,

    I really cannot agree with you. I tried to define a completely new IPsec tunnel.  First test IPsec tunnel had an IPsec policy DefaultHeadOffice (IKEv1) and the second IPsec tunnel had the IPsec policy IKEv2 (IKEv2) and in both cases the IPsec tunnel was correctly established.

    Both appliances were today upgraded to MR2, one appliance I upgraded from v17.0.MR1 and second appliance was upgraded from v16.5.MR8 directly to v17.0.MR2. One appliance has, in addition to the test tunnel, another fully functional IPsec tunnel connected to another appliance with installed UTM v9.506. And this other tunnel is fully functional after updating the XG appliance to v17.0.MR2 too.

    Could you send your IPsec policy screen and I can test your IPsec policy on my test installation. Could not be a problem in the same definition of IPsec policy at the endpoints of the tunnel? Most problems are just the correct definition of IPsec policy and IPsec tunnel (correct IP networks, among others).

    My experience.

    Regards

    alda

  • Hello alda

    Thank god your config is not too sensitive ...  I have a question.  Why would anyone setup a VPN with the 20 (+) years old technology IKEv1 is ?  Now, compare DefaultHeadOffice and DefaultBranchOffice IPSec profiles and you will notice few parameters do not match.  Key Life Phase 1 and Key Life Phase 2 namely.  When I first setup a firewall with CheckPoint in 1991, it was clear in all instructions I read these parameters were supposed to be the same at both end points.  That'S an IPSec requirement.  For one.  One Sophos Senior Support engineer has fixed that on our sites few weeks ago.  He matched every parameters.  I will not argue with an engineer of that caliber.  

    DefaultHeadOffice and DefaultBranchOffice profiles worked in our lab but failed when connected in real life.

    Very basic IKEv2 works with MR1 but once upgraded to MR2 fails.

    Milage may vary they say.

    PJR

    Update:  Reconstructing all VPNs from scratch made them work again.

Reply
  • Hello alda

    Thank god your config is not too sensitive ...  I have a question.  Why would anyone setup a VPN with the 20 (+) years old technology IKEv1 is ?  Now, compare DefaultHeadOffice and DefaultBranchOffice IPSec profiles and you will notice few parameters do not match.  Key Life Phase 1 and Key Life Phase 2 namely.  When I first setup a firewall with CheckPoint in 1991, it was clear in all instructions I read these parameters were supposed to be the same at both end points.  That'S an IPSec requirement.  For one.  One Sophos Senior Support engineer has fixed that on our sites few weeks ago.  He matched every parameters.  I will not argue with an engineer of that caliber.  

    DefaultHeadOffice and DefaultBranchOffice profiles worked in our lab but failed when connected in real life.

    Very basic IKEv2 works with MR1 but once upgraded to MR2 fails.

    Milage may vary they say.

    PJR

    Update:  Reconstructing all VPNs from scratch made them work again.

Children
No Data