Up2Date 9.406003 package description:
Remark: System will be rebooted
News: Security Release
Bugfixes: Fix [NUTM-1616]: [AWS] Change AMI type to HVM Fix [NUTM-4839]: [AWS] AWS Instances in GovCloud need to use S3 buckets in GovCloud Fix [NUTM-5013]: [Network] TCP Vulnerability (CVE-2016-5696)
RPM packages contained: perf-tools-3.12.48-0.237935773.g86aa827.i686.rpm ep-ha-aws-9.40-191.g83c01f2.rb1.noarch.rpm ep-webadmin-9.40-640.g7ad4baa.rb8.i686.rpm ep-cloud-ec2-9.40-26.g00cde1e.rb2.i686.rpm kernel-smp-3.12.48-0.237935773.g86aa827.i686.rpm kernel-smp64-3.12.48-0.237935773.g86aa827.x86_64.rpm ep-release-9.406-3.noarch.rpm
Does not look like the DHCP MTU issue is fixed though?!
Anyone have heard of it?
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)
I have had alot of customers with this issue. The MTU gets set at 576 on the external interface when DCHP is set as the connection method. As you can image, this causes a range of network related problems . Changing the MTU manually drops the connenction altogether.
The solution for me (not ideal) is to roll back to a previous firmware version.
I really hope Sophos fix this soon as im a little over rolling back to previous firmware.