Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
Hello evryone.
after updating Sophos firewall to SFOS 20.0.0 GA-Build222 the DHCP stop relaing ip adress in all network devisies, i try to desabel./enabled DHCP, reload firewall no result.
i was oblige to downgrade to SFOS 19.5.3 MR-3-Build652 and every thing goes On.
someone had this probleme ?
Nope, nothing major it was a config thing - "Fine-tuned the DHCP settings with specific interface as it was configured as "all""
Thanks & Regards,
_______________________________________________________________
Vivek Jagad | Team Lead, Global Support & Services
Log a Support Case | Sophos Service Guide
Best Practices – Support Case
Sophos Community | Product Documentation | Sophos Techvids | SMS
If a post solves your question please use the 'Verify Answer' button.
These are all separate physical ports
I reconfigured the interface in ver 19.5.3-652. That was definitely not fun. It got locked twice and I had to do a factory reset and reload backups. I made sure there was no overlap in the subnets. I think the reason it got locked up is because I missed checking for the same subnet on two different physical ports. The current configuration is shown below. I used CIDR /24 on all ports and gave them a range in DHCP. I may have had some overlap before, but there is none now. All of my devices have access and I can from print from IPhone and Android using apps; they are on different subnets then the printers. I had a lot of static addresses that needed to be adjusted so there was some significant down time. With the new addressing I have tons of space (more that I will ever need) to add more devices. After I verified that everything in ver 19.5.3 worked I upgraded to ver 20.0-222. So far ver 20.0-222 is working, it only been up a couple of hours. No locked ports this time. In the previous scheme I tried to split up the same subnet on several different ports.
I reconfigured the interface in ver 19.5.3-652. That was definitely not fun. It got locked twice and I had to do a factory reset and reload backups. I made sure there was no overlap in the subnets. I think the reason it got locked up is because I missed checking for the same subnet on two different physical ports. The current configuration is shown below. I used CIDR /24 on all ports and gave them a range in DHCP. I may have had some overlap before, but there is none now. All of my devices have access and I can from print from IPhone and Android using apps; they are on different subnets then the printers. I had a lot of static addresses that needed to be adjusted so there was some significant down time. With the new addressing I have tons of space (more that I will ever need) to add more devices. After I verified that everything in ver 19.5.3 worked I upgraded to ver 20.0-222. So far ver 20.0-222 is working, it only been up a couple of hours. No locked ports this time. In the previous scheme I tried to split up the same subnet on several different ports.
