Found out so far, that mailmanager is broken:
Hi, thanks for reporting this issue and sorry for the inconvenience.
We replaced the update from 9.509 to 9.510 (http://ftp.astaro.de/UTM/v9/up2date/u2d-sys-9.509003-510005.tgz.gpg) and also uploaded the update for all who have installed the previous one (ftp.astaro.de/.../u2d-sys-9.510004-510005.tgz.gpg).
I updated the release notes at https://community.sophos.com/products/unified-threat-management/b/utm-blog/posts/utm-up2date-9-510-released accordingly.
- 21 is only half of the truth
Thanks for this, as this up2date only contains:
Up2Date 9.510005 package description:
System will be rebooted
RPM packages contained:
ep-release-9.510-5.noarch.rpm Is it only the "Mailmanager *bug*" that's fixed or have you fixed anything else?
Best regards Martin ;-)
Sophos UTM Certified Engineer v9.7Sophos XG Certified Architect v18.0Homelab: 2 x SG210 XG v18 (HA A/P) - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)
the release contains two additional changes:
@Talex Does this hotfix address any of the dns forwarding logging issues described above?
Yesterday I have installed the hotfix without any issues.
Also the Verification with callout seems to work fine now.Anyone else also installed the hotfix (9.510-5) with success?
Thanks and regards!
The TLS issue appears to be fixed.
Though 'resolver priming query complete' still visible in the 'DNS proxy' logs on my test system.
9.501-5 works fine! THX 4 the hotfix.
With 9.509, I had no problem with the User Portal. With 9.510-5 on my lab UTM, when I login, my username and email address appear at the upper-right, but then it locks up and displays nothing more. A reboot and a restore did not help. Anyone else?
Cheers - Bob
I cant confirm this, UserPortal is working fine as before.
But i have another Issue, dont know if ist from this Version but my config:
I have the Sophos behind a NAT Router in my Testing environement and would like to establish an IPSECL2TP VPN with preshared key. If i do this in the UTM i cant connnect. If i disable IPSEC in UTM and make 3 DNat Rules to a RAS Server in my Network, i can connect and IPSEC/L2TP works fine.
Can someone explain this to me?
I performed the update to 9.510-4 remotely (on my UTM at home), everything seemed to be fine, no issues noted.
Today I update to 9.510-5 remotely, and now the system is off-line and has been for well over an hour....
gonna have to look at this when I get back... :(
XG & UTM Architect (Systems: XG v18 & UTM 9.7 - Virtual, HW & SW)Curious enough to take it apart, skilled enough to put it back together, Clever enough to hide the extra parts when I'm Done!
Different IPsec remote access servers have different levels of security. The UTM's L2TP/IPsec implementation doesn't have the ability to "sign" encrypted packets with the public IP on your router, so your L2TP/IPsec client rejects those packets.