CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add macOS Internet Sharing and Parallels Desktop conflicts for Boundary Client Agent (#5496)

Browse Source 
* docs: add macOS Internet Sharing and Parallels Desktop conflicts for Boundary Client Agent

Updated the "Conflicting Software" section in the Boundary Client Agent documentation
to include issues caused by macOS Internet Sharing and Parallels Desktop (macOS VM with shared networking).
These configurations cause the system's DNS resolver to bind to port 53, preventing the Client Agent from starting.

* chore: change case of macOS to MacOS and added workaround for Parallels macOS VM conflict

* Apply suggestions from code review

approving style suggestions from code review

Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>

---------

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
This commit is contained in:
Mohit KumarDan HeathRobin Beck
 authored and GitHub committed 2025-03-18 17:19:41 -04:00
1 parent 1820d43d38
commit f2c84ad750
1 file changed
+10
Download Patch File Download Diff File Expand all files Collapse all files
website/content/docs/api-clients/client-agent.mdx
+10
View File
@@ -546,6 +546,16 @@ Docker Desktop sometimes creates a local DNS listener that prevents the Client A
If you run Docker Desktop 4.26 or later, you must clear the `Use kernel networking for UDP` option.
Otherwise, the Client Agent refuses to start.
### Internet Sharing (MacOS)
Enabling **Internet Sharing** on MacOS causes the system's DNS resolver (`mDNSResponder`) to bind to all interfaces on port 53, preventing the Client Agent from starting. Disable **Internet Sharing** before you run the Client Agent.
### Parallels Desktop (MacOS VM on MacOS Host)
Running a MacOS VM in Parallels Desktop with shared networking causes the system's DNS resolver (`mDNSResponder`) to bind to all interfaces, blocking port 53 and preventing the Client Agent from starting.
As a workaround, you can configure Parallels Desktop to use a different network mode.
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.
### Palo Alto Networking Global Protect VPN
If you are unable to establish a transparent session while using the Palo Alto Networking Global Protect VPN, you may need to explicitly specify a network interface and the upstream DNS server(s) to use.