Netskope Clients installed on devices (mac and Windows) running VPN apps in full tunnel mode may experience conflicts with 3rd party VPN applications. This usually happens when either app attempts to intercept traffic destined to their respective destinations.
This article lists exceptions to add into steering configurations in order to bypass all VPN traffic to the respective VPN gateway. The configuration changes include the following:
- Creating a Network location policy
- Adding Destination Location Exceptions to Steering Configuration
Creating Network Location Policy
- Login to your Netskope tenant WebUI with admin credentials.
- Go to Policies > Network Location
- Click New Network Location > Single Object
- In the Add Network Location window, enter the following:. . .
- Public IP address of your VPN gateway
- To add multiple addresses, click the + icon and enter the IP address.
- Click Next to continue
- Enter the NETWORK LOCATION OBJECT NAME for your network location. For example, corp-vpn and then click Save Network Location.
Adding Exceptions to Steering Configuration.
You can make the following changes to an existing steering configuration or create a new steering configuration with VPN exceptions.
- Click Settings > Security Cloud Platform > Steering Configuration.
- In the Steering Configuration set up, go to EXCEPTIONS tab > click ADD EXCEPTION and select Destination Network.
- Select the newly created network location.
- Select the Treat like local IP address location to enable traffic (public IP address) bypass to VPN gateway.
- Click ADD EXCEPTIONS and select Domains.
- Enter the name of your VPN gateway. For example, if your VPN gateway is vpn.mycorp.com, enter this and click Add.
- This completes the configuration to bypass your VPN traffic directly to the VPN gateway.