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

v17.1.2 MR2 Release Notes

I see the MR2 has just been released.

 

Any idea what this was about:

 

  • NC-29963 [Firewall] Appliance rebooting with kernel dump

 

I might give it a week or so before updating to see if anyone has issues before making them mine :-(



This thread was automatically locked due to age.
  • Mine takes a while to load but does actually get there eventually.

  • Just swapped over from the UTM to XG today, after a while away, and found the experience both enlightening and quick!

    took me less than an hour to swap over, the 3 x AP50s that I have in a MESH, S2S VPN , and the only adjustment I had to make was for Netflix exceptions, voila all working..

    now I don't have to scroll through pages of Rules, I have them all now on one page, the internet was up in an instant (on PPPoE, way quicker than the last update to UTM)

    A couple of issues around responsiveness seem to have been attended to, although I will have to see how it goes.

    OK, it is a little tardy when initially booting up (but the XG has always seemed a little slower on boot), other than that no issues noted as of yet... if this keeps on going this way I might have to stay with the XG.. and then get the Company to migrate to XG as well.

  • Still don't have IPv6 over PPPoE like there is with IPv4, plus the graphs are still going mental - wish I had this kind of bandwidth...

     

  • Thanks for posting this M8ey I hadn't seen that fix buried in the release notes. This sounds incredibly interesting, especially given the other thread that you and are I posting our latest issues. Hopefully you can get it running on your replaced- unit. It might be related to our problems?

     

    If so I'm in for major trouble because I am stuck on the last 16 release still due to VPN changes that keep an old IKEv1 VPN that I don't control the other end, working. I might try looking into the idea of running two firmwares and trying this latest one to see if VPN will work now as well. Not sure how easy switching to the secondary firmware is, and switching back if it doesn't work right, like if it would mess up VPN certificates or anything or if it's seamless.

     

    Does anyone have any clues about when this issue was introduced and if the ONLY fix is to update to the v17.1.2?

     

    References:

    The other post, listing our support case #'s: https://community.sophos.com/products/xg-firewall/f/hardware/103528/xg210-crashed-today

    The release notes; https://community.sophos.com/products/xg-firewall/b/xg-blog/posts/sfos-17-1-2-mr2-released

  • Hi,

    I can answer one of your questions. Switching back to the previous installed version is very easy, in backup and firmware you click on the install and boot previous version.

    Ian

  • Thank you Ian. Does doing so keep using the same exact configurations? So if I boot with that button to 17.x, but find that it doesn't help, I can switch back to my previous version and the configuration is still the same? Obviously I'll backups configs, but just curious. Thx!

  • Hi,

    I am not 100% sure because from memory the configuration was updated so you might need to restore your configuration in this case.

    Ian

  • "due to VPN changes that keep an old IKEv1 VPN"

     

    I though the VPN issues had been resolved? I am not 100% sure as I don't use a VPN for site to site connectivity.

  • Hello @apalm123

    I can confirm you taht you can upgrade a v16 to v17 and roll it back when you want, it will keep the running configuration.

    But the contrary is not true, if you upgrade, then make changes to the v17, those changes wont be downgraded to v16.

    Secondly, i have VPN's (ipsec) running with v17.1, and it stable (tested with sophos v16, cyberoam and tplink)