is there a roadmap for the XGs for the next major versions and the planned functions?
Forgot to put a follow up/bump here, on the road to XGv18 in two years.
SFOS 17.1.3 MR-3 released these days. Bug fix mostly.
V17.5.b is supposed to be due this week.
Just to keep the thrill alive :)
Two days left, and we are in April ...
My guess is Monday.
Oh !!! LuCar Toni has a very good sense of humor after all ...
So we will get the SFOS v17.5.4 MR-4 on April Fool's day ?
Now after midday, no sign of mr4.
It's 8am in Denmark, we´re still opportunistic ;-)
Best regards Martin ;-)
Sophos UTM Certified Engineer 9.5Sophos XG Certified Engineer 17.1Homelab: 1 x SG210 XG v18 - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)
Ok. That really was on the first of April.
The list of bugs fixes is particularly long and concern quite extensively mails and web filtering. Backups are being forced to have a password. I would have preferred and "opt-out" button.
Besides that, not much new functions.
Installed on XG105 and XG210. Haven't see anything wrong after few hours. But our setup is simple since we are not using anything related to mails (mail gateway is back with Symantec), we have a single VPN, an only a single business rules. Beware, milage may vary.
As far as I know.
~April 24, 2019 there is a large partner conference.
I presume that the event will include announcement, roadmaps, etc.
As far as I know there was also a partner meeting on March 1st, but no news was released after that...
Just upgraded one of our branch office from 17.5.3 to 17.5.4, got some troubles with dhcp (devices doesn't get the gateway ip, ipconfig /renew very slow) and a pppoe connection doesn't came up till i disconnect and reconnect it manually...
Problems start to pop up on XGV17.5.4 MR-4 ...
On Google Chrome 73.0.3683.86, here is what firewall rules look like now :
It happened to me before. But closing the web page and re-opening it would solve it. Not this time. It happens on all firewalls and is now permanent.
i had exactly the same error a while ago. In my case it helped to clear the cache data in Google Chrome. But i think it's the same with other browsers. [;)]
Oups !!! I forgot to clear the cache this time. Annoying to say the least.
I had to do it twice ... Meaning clearing the cache + closing app + testing = failed + clearing the cache again + closing app again + worked this time.
Just a reminder that this is not the thread to post issues that you have with upgrades.