Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 31 subscribers
  • Views 19409 views
  • Users 0 members are here
Options
Suggested
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

A list of items that I think should be fixed in v17.1

rfcat_vk

Hi folks,

 a little list of items in XG that are broken and need fixing either before v17.1 is released or as part of v17.1 - this is based on my usage.

This is not a wish list of things to be added.

1/. IPv6 (bring it up to UTM standard)

2/. reporting - generate the reports at the time they are scheduled

3/. reporting - correct the published date/time reports are generated in the report

4/. change all KBytes etc to standard kbits/mbits/gbits/tbits

5/. fix the values in the usage report so the totals add up correctly.

6/. fix categoristation so that it actually reports categories instead of 16,000 or greater uncatergorised sites daily

7/. change reports to show correct countries, I currently have reports showing my users as sourcing large quantities of data from a reserved address (which is correct 192.168.x.x) and destinations as being other countries.

8/. fix country blocking so that it doesn't block my own country and the US.

9/. fix APs using 5ghz SSIDs (there is an outstanding fix acknowledged by Sophos).

10/. fix the use VLANs in network rules.

11/. fix IPS reports so that my users are not seen as attacking sites

12/. fix logviewer so that is either captures all traffic from internal devices or displays captured traffic. I have had devices trying to connect to the internet but no records show.

13/. fix reports so that they show the traffic from VLANs.

14/. fix the network management report so that it differentiates IPv4 and iPv6 traffic instead of showing the same traffic against both.

15/. fix the dashboard network traffic display (shown as part of the rules) so that the displayed values have some meaning, my links are on a good day 4mb/s and when a users is downloading an update the pink display shows 20,30 or more mb/s

Ian

 

Update - fixed spelling error.



This thread was automatically locked due to age.
Parents
  • 0

    Since v17.1 is almost dev complete, none of these can be considered as feature requests for v17.1.  I don't know what, if any, of them will be resolved in 17.1 since most of them relate to other teams than myself.  However right now is a good time to push for features in 17.2, as the scope is open right now.  So IMO you might get better traction if you say "these are my pain points in 17.0, what I hope will be fixed in 17.1, and are my feature requests for 17.2".

    AFAIK there are no plans for a 17.0 MR6, however high priority defects or security issues could cause one.

     

    Item 6 (categorization) is not tied to any release.  Its a separate issue, a separate department.  Continue to raise it as an "issue" but it isn't really a "feature" per se.  I suspect Country issues are the same thing (assuming it is a GEOIP data issue, not a code/feature).

     

  • 0 in reply to Michael Dunn

    Michael,

     

    Why is there no internal consistency at Sophos?  This KB from 2/6/18 clearly states fixes to follow in 17.0 MR6:

    https://community.sophos.com/kb/en-us/128108

    It is hard to keep waiting for promised fixes to XG that never seem to materialize.  The party line on issues/features since v15 has always been, wait for v16, then it was wait for v17, now I am seeing posts saying wait for v18.  The waiting has gotten old.

     

    Greg

Reply Children
  • 0 in reply to Greg CT

    Greg CT said:

    Why is there no internal consistency at Sophos?  This KB from 2/6/18 clearly states fixes to follow in 17.0 MR6:

    https://community.sophos.com/kb/en-us/128108

    It is hard to keep waiting for promised fixes to XG that never seem to materialize.  The party line on issues/features since v15 has always been, wait for v16, then it was wait for v17, now I am seeing posts saying wait for v18.  The waiting has gotten old.

    I stand corrected.  There is an MR6 planned.  It is mostly IPsec issues.

    As to why there is "no internal consistency" -- I'm a QA who is in the forums in my spare time while waiting for installs.  Nothing I say is an official company statements, it is all "as far as I know".  I do not work with IPsec, I know little about it, I did not know that there was an MR6 planned for IPsec issues.  At the same time, if you talked to someone on the IPsec team, they might not know that the Web team will finish a 17.1 test phase, then will work on two 17.2 features that won't take long, and then immediately jump to v18 while the rest of the company still works on 17.2 and 17.3.

    At no time in this post am I saying "wait for v18".  I don't know anyone who is saying that.  Unless it is customers who are saying "The feature I want is not in v17, I guess I'll wait for v18 and hope it is there".  That is not a company promise that we are going to add something in a particular version.  Sophos has actually been pretty good (AFAIK) at delivering what they promise to deliver.