We'd love to hear about it! Click here to go to the product suggestion community
I was one of the users who originally reported an issue with the IPS function and WiFi with the EAP -- after the new version was applied, and IPS function re-enabled in the policy, tested again, and same behavior; boot laptop, wifi works for a couple of minutes, then all useful traffic stops (still connected, just no DNS, etc.). Disconnecting/reconnecting the wifi has no effect; going into Central, disabling IPS in the applicable policy, and rebooting the laptop corrects the issue. I have a SDU that has data surrounding the timeframe of the test if anyone at Sophos is interested. Endpoint client shows the following current versions:
Core Agent: 2.5.5 Beta
Endpoint Advanced: 10.8.6.215
Sophos Intercept X: 2.0.16 BETA
Forgot to add, the wireless adapter in this laptop is a Qualcomm Atheros QCA9377 Wireless Network Adapter
In reply to BrucekConvergent:
Thanks for reporting the issue. If you can send us the SDU log we'll look into it and follow up.
In reply to Vincent Vanbiervliet:
How / where do you want this sent? It's about 17MB. Is there an upload portal, etc. you want this sent to?
Hey Vincent, any update on this issue I reported? Last I heard from you was the developers were seeking a similar model laptop to mine (the SDU did not help them)….
Apologies for the delay in answering. So far we have not been able to reproduce the issue.
If you haven't done so yet, would you mind trying again with the latest refresh? We have fixed some things, and engineering is hoping it would also tackle this problem. At a minimum it should give us some telemetry that can help us.
Vincent, is there something newer than the version numbers I posted at the top of this thread? updates on the client don't reveal any updates to the version numbers of any component (I've been using the laptop all along, just with IPS off so WiFi works).
Can you please verify the version of "Sophos Network Threat Protection"? Latest version should be 1.9.2235.0.
Double-click the systray icon, then "About", "Run Diagnostic Tool". In the new window, select "Installed Components".
It appears that the issue may have been fixed -- I guess a smaller update that didn't change the actual version numbers (maybe indicated by your request) must have fixed it. Thanks!
That is good news, thank you for the feedback!