This article is targeted at administrators who desire to disable the Umbrella roaming client on their corporate networks and enable it off the corporate network. If you do not desire to back off the roaming client on network, stop here.
The Umbrella protected networks feature is intended for a single egress network. For any networks with more than one egress, an alternate feature is required.
Today, this feature exists in production as the trusted network domain feature; however, must be configured on the Umbrella back end. Read on to learn how to request the feature and what is required on your network.
What is the Trusted Network Disable feature?
The trusted network by domain feature is a way to disable the roaming client on your corporate network, but keep it enabled off network. When activated, the feature will:
- Disable DNS protection provided by the roaming client
- Defers policy to the network policy
- Stop all network probes except the trusted network domain check
- Great for busy networks!
- Great alternative to the VA backoff
- Use in conjunction with VAs for less network talk
- Defer IP Layer settings to the network policy
IPv6 Behavior, Windows versus macOS
- On Windows, the domain is queried on IPv4 and IPv6. The shut-down behavior is handled separately on each network stack. For example, if the domain resolves on IPv4 but not IPv6, then the roaming client will shut down on IPv4 only, and stay operation on IPv6. If you wish to have the client shut down completely, then IPv4 and IPv6 queries must resolve.
- On MacOS, the domain is queried on IPv4 and IPv6. Unlike Windows, if the domain resolves on either network stack, then the roaming client will shut down for both IPv4 and IPv6.
How do I enable the feature?
Today, this setting exists in the back end only. It is fully production and is slated to arrive in the dashboard in the future.
To request this feature, open a support case to email@example.com and request the trusted network domain feature. Provide us with:
- The desired Umbrella disable subdomain. This domain must:
- Have an A record that resolves to a RFC-1918 internal IP address (for IPv4)
- Have an AAAA record that resolve to an RFC-4193 IP on IPv6 (if IPv6 is used)
- RFC-1918 IPs typically look like 10.x.x.x, 172.x.x.x, or 192.168.x.x
- RFC-4193 IPv6 addresses start with 'FD'
- The IP addresses do not have to be reachable
- Must be a subdomain
- sub.domain.com - good!
- subdomain.com - no good.
- Resolve off network to NXDOMAIN, NODATA, or public IP address (so the client remains enabled in this scenarios)
- No SERVFAIL please
- Be a domain in a zone you control to ensure you control the public and local space
- Umbrella Roaming Client
- AnyConnect Umbrella Roaming Security Module 4.5 MR4+ only
How do I test the feature for one machine?
To test locally before having the Umbrella team apply the setting globally, apply this override.
- Create a file "customer_network_probe.flag"
- Ensure the file is not .flag.txt
- Put the desired domain into the contents of the file
- Place the file into:
- Roaming client
- Windows: %ProgramData\OpenDNS\ERC\
- MacOS: /Library/Application Support/OpenDNS Roaming Client/
- Windows: %ProgramData%\Cisco\Cisco AnyConnect Secure Mobility Client\Umbrella\
- MacOS: /opt/cisco/anyconnect/Umbrella/
- Roaming client
- Restart the roaming client
- Roaming client: https://support.umbrella.com/hc/en-us/articles/230561067-Umbrella-Roaming-Client-Manually-Disabling-or-Restarting-
- AnyConnect: Restart the parent vpnagent AnyConnect service