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

v17 VS v18: things that are just a step backward

Dear Community,

I already had the possibility to present v18 to some customers in a live demo and showed them the changes made into v18. The features are very welcome and "approved" by the customers but the problem is how these features are implemented.

  • DNAT: customers really liked the way Sophos was allowing the creation of DNAT Wizard. Sophos wanted to follow the competition instead of creating their own product. Also, the DNAT wizard windows is very raw. Current DNAT is very copy and paste from other vendors and it is a step backward compared to BAR implementation
  • Current DNAT wizard: the wizard creates loopback and reflexive rules automatically, so all the time you need to delete them. The Wizard does not enable logging by default, does not allows you to select IPS profile and it is enabled by default
  • If you delete the DNAT firewall rules, it does not delete the associated DNAT rules. Really? This is another example of bad design/implementation!
  • WAF: WAF is under action. Dear Sophos this is very bad design! I am sure a lot of customers will complain this as it is not straightforward. The success of ASTARO was simplicity while XG is complicated
  • SD-WAN: for SD-WAN, users need to move between 3 tabs and 2 menu (firewall, nat and SD-WAN under Routing). This is another example of bad design and copy and paste example. In my opinion, I would have renamed Firewall tab to Policy tab and
    • Leave the BAR
    • Create a new wizard with SD-WAN policy where linked NAT creates the associated NAT.
  • Icon inside firewall rules: it was straightforward to recognize a BAR rule vs a standard firewall rules. We have filters but sometimes a simple scroll down (specially when the rules are fewer than 20, you can on the fly recognise the BAR instead of reading all rules now or using filters
  • DPI vs PROXY: the 2 checkboxes create a lot of confusion. To be honest I do not have an idea how to improve this point.

Community users what do you think?



This thread was automatically locked due to age.
Parents
  • Hello,

    the version 18 brought a lot of complexity into the XG solution. I totally agree that the individual functions are great, but the implementation into the GUI is too complicated.

    I also agree that with Astaro the simplicity of the solution was always the strongest attribute, but now with XG18 it is not.

    Also I believe, that Sophos wrongly interpreted why partners fight againts this, as imho Sophos believes, that partners says we don't understand it, but they say

    it is too complicated for administration, because of separation of the most important information between multiple tabs and screens.

     

    Compare with me:

    Version 17.5: One single screen with FW rule, NAT, WAN balancing.

    Version 18: The very minimum is 3 different tabs (FW rule, NAT and SD-WAN) just to see what you will achieve.

    Just to see, which IP addresses you will end up with NAT is almost impossible. For every firewall rule you need to check it independently ... crazy.

     

    We want to see it and best also select it directly in the firewall rule creation!

     

    Btw. DPI and proxy - I would just create select button with "DPI" and "Standard proxy", that is all.

    Jindrich Rosicka

    awin IT

Reply
  • Hello,

    the version 18 brought a lot of complexity into the XG solution. I totally agree that the individual functions are great, but the implementation into the GUI is too complicated.

    I also agree that with Astaro the simplicity of the solution was always the strongest attribute, but now with XG18 it is not.

    Also I believe, that Sophos wrongly interpreted why partners fight againts this, as imho Sophos believes, that partners says we don't understand it, but they say

    it is too complicated for administration, because of separation of the most important information between multiple tabs and screens.

     

    Compare with me:

    Version 17.5: One single screen with FW rule, NAT, WAN balancing.

    Version 18: The very minimum is 3 different tabs (FW rule, NAT and SD-WAN) just to see what you will achieve.

    Just to see, which IP addresses you will end up with NAT is almost impossible. For every firewall rule you need to check it independently ... crazy.

     

    We want to see it and best also select it directly in the firewall rule creation!

     

    Btw. DPI and proxy - I would just create select button with "DPI" and "Standard proxy", that is all.

    Jindrich Rosicka

    awin IT

Children
No Data