keye-network-optimizer

Keye Network Optimizer

Use this workflow on macOS. Preserve connectivity, proxy access, VPN access, and remote sessions while collecting comparable evidence.

Non-negotiable safety rules

• Follow this order: diagnose, make the smallest reversible change, retest.
• Never run destructive resets such as deleting network services, removing VPN profiles, resetting all network preferences, or unloading system daemons.
• Do not use sudo, disable a VPN/TUN/proxy, change MTU, or terminate a process without first explaining the effect and obtaining user approval.
• Treat a user requirement to keep a proxy for GFW access as a hard constraint.
• Record the current value and an exact rollback command before every change.
• Do not hardcode interface names, gateway addresses, proxy ports, DNS winners, or network service names from a previous run.
• Run throughput, ping, DNS, and traffic sampling sequentially. Concurrent tests create load and invalidate latency and packet-loss comparisons.
• Keep before and after conditions identical. A TUN-on versus TUN-off comparison is a separate A/B test and must be labeled as such.

Phase 1: establish scope and safety

1. Confirm the host is macOS and note whether the user is local or connected through SSH, Screen Sharing, a VPN, or another remote-control path.
2. Ask whether proxy/VPN/TUN connectivity is mandatory if the user has not said.
3. Ask other users and applications to pause large transfers for the baseline.
4. Create a timestamped evidence directory and keep raw before/after outputs.
5. Do not make changes until all required before measurements are complete.

Use shell variables with task-specific names. If a multi-line snippet uses Bash arrays, run it with bash -lc rather than relying on zsh behavior.

Phase 2: collect the before baseline

Collect these snapshots first:

sw_vers
scutil --nwi
route -n get default
scutil --dns
scutil --proxy
networksetup -listallhardwareports
networksetup -listallnetworkservices
networksetup -listnetworkserviceorder