Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 31 subscribers
  • Views 19395 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,

    If you look at Ian's first statement these are things that we have seen that are still broken and need some focus on getting corrected and are not feature requests. I had posted a feature request  but after Ian pointing out he was trying to make this a list of things that needed to fixed I deleted my post to keep the thread on topic.  Hence the reason for my deleted post showing up in this thread.

    I appreciate you keeping us all up to date with what you know and its progress.

     

    -Ron

  • 0 in reply to rrosson

    rrosson said:

    Michael,

    If you look at Ian's first statement these are things that we have seen that are still broken and need some focus on getting corrected and are not feature requests.

     

    Agreed.  I should not have said feature requests.

    I was focusing on his statement "need fixing either before v17.1 is released or as part of v17.1" and I was trying to say that 17.1 is scope complete. Therefore this list (of needs fixing, not feature requests) cannot be considered as a new input for deciding what will be included  in 17.1. Maybe some of them will be addressed - I don't know. But if anyone wants to make input into the scope of an 17.1 MR or of 17.2, now is the time to do it. Whether Product Management sees those scope requests and how they balance them against other priorities is not for me to say.

     

    One thing I should mention, because I don't know if Sophos has made it entirely clear...

    We try not to bring out Features in a maintenance release. So if we do an MR1, MR2, etc those generally will always contain bug fixes. There are a bunch of features we want to bring out before v18, so Sophos has decided to do a 17.1 17.2 and 17.3 as mini feature releases. The .1 (etc) releases will have bug fixes in them as well, but the main focus is features. This was demonstrated in 16.5 when Sandstorm was a feature released between v16 and v17.

    So in the next year, I would expect to see every month or so either an MR or a .x release, depending on whether the focus is bug fixes or features. I don't know if that really helps you guys, but it is something to keep in mind when doing your wishlists or scope requests.

  • 0 in reply to Michael Dunn

    Does the Sophos team plan on keeping the SFM updated with the latest XG firmware compatibility?

     

    The SFM hasn't been able to manage v17 MR 5 templates, and I haven't found any other mention of this aside from others asking without getting a response.

     

    Was Sophos XG v17 MR 5 released prior to being supported by the SFM due to the nature of the release?  There were a lot of bug fixes included in MR 5, so it would make sense for Sophos to release that even before the SFM can fully support the templates for it.  From the customer's perspective however, I expect that if a firmware update is released, it should be fully supported by the SFM immediately.  Can someone please clarify what the customer should expect with using the SFM?

Reply
  • 0 in reply to Michael Dunn

    Does the Sophos team plan on keeping the SFM updated with the latest XG firmware compatibility?

     

    The SFM hasn't been able to manage v17 MR 5 templates, and I haven't found any other mention of this aside from others asking without getting a response.

     

    Was Sophos XG v17 MR 5 released prior to being supported by the SFM due to the nature of the release?  There were a lot of bug fixes included in MR 5, so it would make sense for Sophos to release that even before the SFM can fully support the templates for it.  From the customer's perspective however, I expect that if a firmware update is released, it should be fully supported by the SFM immediately.  Can someone please clarify what the customer should expect with using the SFM?

Children
No Data