Known Issues In Release 118.0.0
Known Issues In Release 118.0.0
Here is the list of known issues in this release.
| Issue Number | Category | Description |
|---|---|---|
| 470558 | CASB Real-time Protection | Google Meet is using Google Custom Protocol QUIC, RTCP, STUN over UDP instead of TCP and it is using HTTPv3 over QUIC for communication. Hence, Post activity on Google meet app connector will have detection issues. |
| 132227 | CASB Real-time Protection | In Google Calendar, the downloaded bigger files are not getting the file size policies. |
| 472680 | Cloud Firewall (CFW) | If firewall service does not identify the application name and discards the session before IPS matches signatures, IPS will have application name as “Unknown” in IPS event. In these cases, where IPS event may not have an app name, but Firewall can have an app name, it can be found with session details. |
| 423457 | Netskope Secure Web Gateway (NG SWG) | Rules with filefilter conditions might not be considered when they followed a content inspection rule with a traffic action. |
| 322097 | Netskope Private Access (NPA) | When the CASB traffic steering mode is set to None, the macOS users are unable to disable NPA tunnel since the option to disable Client gets disabled. |
| 322094 | Netskope Private Access (NPA) | NPA Block notification will not be displayed to end user when Client is configured as NPA only mode or CASB traffic steering mode set to ‘None’. |
| 488897 | Netskope Private Access (NPA) | SRPV2 is not supported by a local broker. |
| 17170 | Remote Browser Isolation (RBI) | RBI was not showing the Read Only pop-up message again after a redirection to a new webpage in isolation. |
| 470467 | Traffic Steering | Since version 114.0.5, the Docker pulls failed as the Docker proxy process is unable to handle a force reset in a closing connection. |
| 466448 | Traffic Steering | With self protection enabled, when the tokens change in a tenant, the MSIEXEC command (for example, msiexec /I NSClient.msi mode=peruserconfig host= <tenant-name>.goskope.com token=<token ID> enrollauthtoken=<new authentication ID> enrollencryptiontoken=<new encryption ID>) failed to update the tokens while repeating the Client installation using the new tokens. As a workaround, use nsdiag to update the secure enrollment tokens. |
| 438566 | Traffic Steering | Netskope does not support TCP/DNS response handling when DNS responses are received through the tunnel when the DNS Security is enabled. |
| 225028 | Traffic Steering | To enable DNS security in web mode, Netskope client tunnel should be re-established. Netskope client detects the DNS traffic enable flag from web UI and then checks for the CFW availability on tunnel establishment. If CFW is available then the Netskope client starts the DNS security. Netskope Client also re-established the tunnel upon machine restart, shutdown, network change and enable/disable of Netskope client. |
| 301400 | Traffic Steering | Netskope Client status is not updated because of the incorrect format. |
