Diagnostic reports accuracy

XG has become too complicated and dare I say bloated at the moment and without comprehensive logging, very difficult to troubleshoot. I am sure the problems that you notice will be fixed in future releases but that has been the history of XG... always promising future improvements. Problem with that strategy is that when the next version comes and they fix 100 previous bugs, people don't give them enough credit for under the hood fixes.

They are pushing regular EAP updates and have fixed a lot of bugs atleast from the update notes. Lets see how many things are fixed before the GA. I think all their resources are being used on fixing DPI at the moment which is the main selling point of XG v18. I am still not happy with the unexpected results in NAT rules but that could just be my testing methodology. NAT Rule zero needs revisiting for sure.

Regards

Hi Billybob,

the stats have been broken for a long time and should have been fixed.

I like the new disable NAT rule 0 function, interestingly when you disable NAT rule 0 in IP4 it appears to be automatically disabled in IPv6.

I agree there are lots of fixes in the latest version which is good.

Ian

Hello rfcat_vk,

Thanks for the feedback.

I am sending you the PM to get details to understand the issue.

Hello rfcat_vk,

Thank you for the feedback and information provided to understand issue.

We are going to take improvement for average client count and tracking with NC-55945.

WAN zone usage in Diagnostic reports are populated with data transferred from then WAN zone which cannot compare with browser download speed.

Thanks you,

Jekin

Hi Jekin,

thank you for the followup. I am seeking clarification based on your answer. What you are saying is the diagnostic display is correct but at odds with the GUI, the MBP (activity monitor) network connection and the browser speed test result?

Ian