Skip to main content
Solved

Wrong gateway--bom1.goskope.com

  • December 11, 2023
  • 2 replies
  • 472 views

Forum|alt.badge.img+1

Dear Team,

 

For the Mac user's Netskope client installation, we are getting the wrong gateway on the user's client configuration as the "gateway-bom1.goskope.com". 

The traffic is not tunneling through the Netskope tenant but the client configuration is showing as an enable.

 

We also have not received the logs in Skope-IT alerts for all Mac users.

 

In nsdebuglog.log, found the error as "failed to open file for reading: /Library/Application Support/Netskope/STAgent/l4config.json, err:2"

 

Kindly help us on this issues. 

Best answer by Shraddha_Tupe

Hi @jforrest ,

 

Yes, I need to open the support case on the same.

In the TAC team's analysis, they've mentioned it is faced by us due to the "0.0.0.0/n" bypassed IP ranges and they provided the below comment on ticket itself : 

 

We made a change back in R105 in how we handle IP exclusions/bypasses at the client level: "Before R105, our exclusions by IP applied only to ports 80 and 443, so there was no way to exclude the entire IP. If IP is on the list, it will be excluded for all ports." Because of this change, MacOS is now giving us errors when trying to add in IP rules for certain IP-based exceptions, specifically IP rules for network objects "0.0.0.0/n".

This topic has been closed for replies.

2 replies

jforrest
Netskope Employee
Forum|alt.badge.img+12
  • Netskope Employee
  • January 2, 2024

Hello @Shraddha_Tupe ,

 

Could you open a support case on the same so the team can work with you to triage this? https://support.netskope.com/


Forum|alt.badge.img+1
  • Author
  • Netskope Partner
  • Answer
  • January 3, 2024

Hi @jforrest ,

 

Yes, I need to open the support case on the same.

In the TAC team's analysis, they've mentioned it is faced by us due to the "0.0.0.0/n" bypassed IP ranges and they provided the below comment on ticket itself : 

 

We made a change back in R105 in how we handle IP exclusions/bypasses at the client level: "Before R105, our exclusions by IP applied only to ports 80 and 443, so there was no way to exclude the entire IP. If IP is on the list, it will be excluded for all ports." Because of this change, MacOS is now giving us errors when trying to add in IP rules for certain IP-based exceptions, specifically IP rules for network objects "0.0.0.0/n".