First impression and feedback

Hi All,

I migrated my home box from MR7 to v17 and all good.

In my case, the IPS did not start automatically after the reboot.

The other thing is the UI is faster than v16 but the Network menu is very slow compared to the others. I have only 2 NICs and 2 VLAN.

Last thing, where is the policy test?

  • Hello,

    I agree with rfcat_vk and lferrara too that the font in a firewall packet rule should be a little bigger. 

    Is it possible to vote somewhere?

    ;-) 

    alda

  •  

    adjusting the zoom cannot be used because if you adjust the zoom for firewall rule, then the Web Policies will be too big. I guess you need to adjust the resolution a little bit, guys.

    Also consider, please, to exploit the white space on the left and on top. Compared to v15 and to v16, guys, you improved the GUI alot. Having even a link of policy test inside Diagnostics should make sense.

    IPSEC Profiles? Well done. I hope you will re-design most of the tab like that. Please move the NAT tab in another place. Under profiles, is really wasted and it does not make sense.

    All the time, I need to explain to customers where the NAT tab is.

    Thanks

  • The new firewall rule view is great!Reminds me very much of the Fortigate view ;)

  • We'll look at the font size with our designers, and see what can be done. 

    IPSec page changes are the first place we are able to implement a new UX framework. It's actually a sneak peek of some of the benefits coming later next year, where we will move everything to an improved web framework. With that, we can consider a fully responsive design, that maximizes use of available screen space, but we won't consider it before then. 

  • Very good, because that missing response design is actually the only thing we are currently lacking in terms of web design.

  • I agree - they need to utilize the full browser width and increase the font sizes. Very difficult to read.

  • That network menu is a complete killer. We need to have a collapsible menu like it was in the Cybers. If you need to get to any other tab in that network menu when you have 8 interfaces with 20 VLANs in each you wait a day for it to process. Then if you have to go back to interfaces and away again the process is too long. When you are building an environment, even a smaller one, the additional time it takes to navigate the UI is very costly.

    Thanks

  • Hi All,

    in my personal opinion i will change:

    - NAT and WAF Rules on different pages. Firewall ACL is another security concept

    - on Dashboard no Health status about Power redundancy

    - on Dashboard no Health status about disk, or mirror disk. Only one way to discover problems is to go on DataCenter room and listen to the alarm...

    - on Dashboard on Web Hits, we would see the number of HTTPS connections and HTTP

    - We need a full log export, in case on Deep analysis on Forensic analysis. Reports are goods for Executive and for POC but you partner need to be able to answer who did what,when, wich protocol and wich port where used.

    - IPS Engine/Policy. If you need to exclude a single signatures only for a restricted number of users/pc you need to create two rules and play with priority: ok, but if you are on middle market customer how many rule you need to do to secure the customer? This is the same for Application policy

    - About metrics, decide to Use Kbit (kb)or KByte (KB), but with the right Sintax.....If you play whit BWM too many misunderstanding on the GUI and Documentation

    - Help us with O365 creating an Hidden Feed RSS to automate the download and the population of O365 IP/FQDN service to exclude from Proxy. Too many errors and problems about it.

     

    Thanks

  • I have always complained about the static gui. It shows very limited information and most of it is not important as a snapshot. Also completely agree with kilobit and kilobyte problem. It is really not that difficult... ALL live traffic including QoS rules should be in kilobit/mbit since we get the traffic from our ISP in kilobits/megabits and our network cards are also in megabits/gigabits etc. However the aggreagate traffic, like how much traffic did TOM use or the total amount of traffic should always be in kilobytes/megabytes etc. Maybe v18...

     

    Edit: On a side note, I have a different bug report about the firewall passing all traffic as soon as it is connected to the network. Did you guys know about this behavior? It has been there since v16[:#] https://community.sophos.com/products/xg-firewall/sophos-xg-beta-programs/sfos-v170-beta/f/sfos-v170-beta-issues-bugs/96108/bug-firewall-starts-passing-all-traffic-before-running-the-wizard 

  • Why not v17 GA or v17.1? : )

    Billybob said:
    I have always complained about the static gui. It shows very limited information and most of it is not important as a snapshot. Also completely agree with kilobit and kilobyte problem. It is really not that difficult... ALL live traffic including QoS rules should be in kilobit/mbit since we get the traffic from our ISP in kilobits/megabits and our network cards are also in megabits/gigabits etc. However the aggreagate traffic, like how much traffic did TOM use or the total amount of traffic should always be in kilobytes/megabytes etc. Maybe v18...

    Edit: On a side note, I have a different bug report about the firewall passing all traffic as soon as it is connected to the network. Did you guys know about this behavior? It has been there since v16[:#]