Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Firewall: v20.0 GA: Feedback and experiences

Release Post:  Sophos Firewall v20 is Now Available  

The EAP Post:  Sophos Firewall: v20.0 EAP1: Feedback and experiences  

The old V19.5 MR3 Post:  Sophos Firewall: v19.5 MR3: Feedback and experiences  

To make the tracking of issues / feedback easier: Please post a potential Sophos Support Case ID within your initial post, so we can track your feedback/issue. 

Release Notes:  https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_200_rn.html 



This thread was automatically locked due to age.
Parents Reply Children
  • Hi  ,

    It is currently in our backlog but not prioritized for the near term. We haven't received many requests for the support of DHCP-PD for VLAN / LAG. Do you perceive this as a common deployment scenario?

  • Hi. In my network scenarios, yes. Typically, I will connect the firewall to a core switch via a LACP LAG. This is because the firewall is being used for L3 routing between local networks for high bandwidth applications, high speed Internet, etc. Also allows for redundant configs for varying degrees. All networks, for various purposes and uses are provided over the LAG with VLANs to the switching gear.

  •   I understand you may not have received many requests for it, but as I have stated to the Sophos team over and over again, why implement a new feature that only partly works? If the feature works for a physical interface, there is no reason it shouldn't work on a LAG as well. That's just stupid for any feature. As more networks need higher availability, LAG will be used more and more. Make the features work on both.