From dfc638ff89870e7b35f326e66d053b45a3579367 Mon Sep 17 00:00:00 2001 From: komal-hashi Date: Tue, 9 Sep 2025 22:55:08 +0530 Subject: [PATCH] updating the doc with anyconnect vpn conflicting software (#5989) * updating the doc with anyconnect vpn conflicting software * addressed pr comments * done some minor formatting --- .../client-agent/conflicting-software.mdx | 25 ++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/website/content/docs/client-agent/conflicting-software.mdx b/website/content/docs/client-agent/conflicting-software.mdx index 320300b025..9929e45767 100644 --- a/website/content/docs/client-agent/conflicting-software.mdx +++ b/website/content/docs/client-agent/conflicting-software.mdx @@ -203,7 +203,30 @@ As a workaround, you can configure Parallels Desktop to use a different network Select an alternative network configuration such as **Host-Only**, **Default Adapter**, or **Wi-Fi** instead of **Shared Network**. Refer to the Parallels Desktop documentation for more information. +## Cisco AnyConnect VPN + +When the Cisco AnyConnect VPN is active at the same time as the Boundary Client Agent, DNS resolution may fail for Boundary aliases. + +The Boundary Client Agent by default uses the IPv4 range `100.x.x.x` for its local proxies. The Cisco AnyConnect VPN treats this range as a **secured range**, which forces DNS queries to resolve through the VPN instead of the Boundary Client Agent. As a result, Boundary aliases cannot be resolved. + +You can configure the Boundary Client Agent to use a different IPv4 prefix by setting the `v4_prefix` option in the client configuration file. This setting overrides the default `100.x.x.x` range and avoids the conflict with Cisco AnyConnect VPN. + +For example: +```hcl +v4_prefix = "172.16.0.0/12" +``` + + +You can set the `v4_prefix` to any valid RFC1918 private IPv4 range, as long as it does not overlap with ranges secured by the VPN. Common options include: + +- `10.0.0.0/8` +- `172.16.0.0/12` + +Choose a range that best fits your environment. + + + ## Uninstall the Client Agent on Mac If you used the Mac installer, you can run `/Library/Application Support/HashiCorp/Boundary Uninstaller.app` to uninstall Boundary. -The uninstaller removes any installed components, including the Desktop client, CLI, and the Boundary Client Agent. \ No newline at end of file +The uninstaller removes any installed components, including the Desktop client, CLI, and the Boundary Client Agent.