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.
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.
Do you know when the files will be updated so can be manually updated?
My 105 has picked up the update, but the two VMs I have for testing are not yet. The ISO's that are available are only MR1 spec.
Thanks.
Hi RichardPhillips,
you can download from Firmware Updates
https://secure2.sophos.com/en-us/mysophos/my-account/network-protection/firmware-updates.aspx
Hej,
can I update directly from v16.5 MR-8 to v17 MR-2?
Thanks.
Rodrigo Pereira said:NC-19881 [Mail Proxy] Whitelist and blacklist for e-mail/domains in WebAdmin.
Are we sure this made it into MR2?
I have a test VM that I keep up to date to check on the progress of XG in hopes that I can migrate my UTM 9.x system soon and I do not see this anywhere. I also looked at a hardware install that I have of XG and can not find any sign of whitelist/blacklist management from both WebAdmin and User Portal. If I am looking in the wrong place please point me to where it can be found. Also there is no mention of how this was implemented. I am hoping it is like it is done in UTM to where it can be done either at the administrative level or the end user can maintain the blacklist/whitelist from the user portal.
This is one of the features that are holding me back from migrating to XG from UTM 9.x
All systems mentioned above are Home licensed installs.
TIA
-Ron
Not sure if it makes a difference in Home licence, but my home xg105w now has more options in general settings in MTA mode....
So its there, but hopefully it works. :-)
EDIT - Just did a quick check with the block list, and it works fine. To block (and probably whitelist) you can enter the individual address, or wildcard "*@domain.com"
Interestingly...I'm only seeing this problem(problem using manually created encryption policy) on one XG135. I have another one that does not have this issue, but it doesnt have an active VPN going like I did on the first one. Going through the creation process on the second unit I can choose a manually created ipsec/encryption policy. I've opened up a support ticket, hopefully they can give me an answer.