XG v17.5.4 MR4-1 Released (MR4 update 1)

After updating from 17.5 MR3 to MR4, my UI becames much faster than before... Additionally, in my DHCP Settings, the Option "Use device's DNS settings" was unticked after upgrade... So my DHCP was not delivering any DNS Server Information what caused my clients to not being able to resolve names... 

Anybody else had this issue? I don't know currently what else might be broken with that release...

I presume you upgraded to SFOS xg17.5 MR4-1 (17.5.4.429).   Were you able to "tick" it back ?

Paul Jr 

My Firewall is currently running on 17.5.4.409. I could go back, but i re-set the option again, and afterwards it worked again.

Stupid question like this: Why don’t you upgrade it to 429 ???? Since it fixes a major bug you mentioned earlier ?

Paul Jr

Because if i would do so, and If i would find another "bug", I wouldn't be able to go back to 17.5 MR3.

But you are running 17.5.4 already !!!  And if you did your BU properly, you can always return to MR3 any time.  It is a pain since you would have to wipe your firewall to OEM,  and then re upgrade to 17.5.3 and then import de v17.5.3 MR3 BU file, but is still feasible.

Paul Jr

Hello @HuberChristian,

If you have upgraded 17.5 Mr-4-0 before then you may simply roll back to 17.5 Mr-3 and replace the non-active firmware i.e. 17.5 Mr-4-0 with the latest 17.5 Mr-4-1 and perform the upgrade. In case you are encountering any issue with the latest version, you may simply roll back to 17.5 Mr-3. 

Please bear in mind that the backup of the later firmware version will not able to restore on lower firmware.

As a precision.  Let say you see firmwares 17.5.4 MR4-1 (i.e.429) and 17.5.4 MR4 (i.e.409) listed.  And you want to go back to 17.5.3 MR3, you can upload and replace anyone of both firmwares already listed.  For example, in the end, you could have  17.5.4 MR4-1 (i.e.429) and 17.5.3 MR3 (i.e.372) listed. 

Then, once you have replaced the firmware, you get this: 

Obviously, when you revert to 17.5.3 MR3, your appliance will load factory defaults and you will have to upload a 17.5.3 backup.  If you haven't made a BU, you will have to punch all your configuration manually !!!!  Ouch !!! So make sure you have a backup matching the SFOS version you want to restore to.  I'm almost certain you knew that already.

Paul Jr

As a precision.  Let say you see firmwares 17.5.4 MR4-1 (i.e.429) and 17.5.4 MR4 (i.e.409) listed.  And you want to go back to 17.5.3 MR3, you can upload and replace anyone of both firmwares already listed.  For example, in the end, you could have  17.5.4 MR4-1 (i.e.429) and 17.5.3 MR3 (i.e.372) listed. 

Then, once you have replaced the firmware, you get this: 

Obviously, when you revert to 17.5.3 MR3, your appliance will load factory defaults and you will have to upload a 17.5.3 backup.  If you haven't made a BU, you will have to punch all your configuration manually !!!!  Ouch !!! So make sure you have a backup matching the SFOS version you want to restore to.  I'm almost certain you knew that already.

Paul Jr

Hello Big_Buck 

The configuration before the upgrade will still remain on your firewall. It should not go back to factory default (unless you have not configured it in Mr-3).

Maybe, but every time I tried, it failed ...  In the case I pictured above, I have manually forced a firmware to replace what was the previous firmware.  I.e. I replaced MR4 with MR3.  MR4 was the previous to MR4-1. MR4-1 remained active, in place, and listed.  So.  I do not believe that while I was uploading MR3, the corresponding configuration came along with it.  So.  In this case, I believe we have to upload MR3 firmware, than we have to upload the MR3 backup.

Paul Jr

Hello Big_Buck,

The SFOS would keep two sets of configurations with ties to their respective firmware.  Now if you override with another firmware, the configuration and the firmware are both removed from the system and in this case, the only option is to upload the older firmware again. At this point, the backup from the higher version will not be compatible with the lower version. So it will be factory reset to default.

So, if I have followed correctly, as we speak, Hubert should have two firmwares, MR4 (409) and MR3 with corresponding backups.  (He did not upgrade to MR4-1) If he did not made much changes that he could repeat, he could then load MR3 firmware (i.e. make MR3 firmware active), then upgrade MR3 directly to MR4-1 (which would replace the unactive MR4 (409) firmware with the more recent MR4-1 (429) firmware).  That way, he would have a local, synchronized, and attached backup of both MR3 and MR4-1.  That would then allowed him to swap from on to the other ...

Right ?

Paul Jr

Hello Big_Buck 

Yes, that is correct.

Will 17.5.4 MR4-1 fix local routing mail errors ?

Local mail xg@company.de to remote adress user@company.de fails..

Hello juergenb52,

You have an ongoing issue on another thread. Let's stick our conversation on that post.

Aditya,

it seems that Sophos has implemented a Buggy exim with 17.5.4 and even with 17.5.4-1.

With 17.5.4 i can´t get the XG Backup files through mail.

For my expirience, the QS is not doing it´s Job.
This XG 17.5.* gets even worse with every new MR.

I talked to a friend yersterday and they don´t like to sell the XG Version.
To many Problems and a lot of Features from UTM are still missing.

In fact, i have no issues right now in all of my implementations. 

Basically you see only the people having issues with a product than the other percent, which works perfectly fine. 

My Backups getting send without any issue etc. 

And changing a daemon can be problematic for certain installation. 

I do not want to open the XG vs SG discussion right now. 

Hi Toni,

when will Sophos fix the buggy 17.5.4-1 Release?