Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -456,3 +456,4 @@ sudo /opt/socket_vmnet/bin/socket_vmnet --vmnet-mode=host --vmnet-network-identi
- To enable verbose debug logs, set the environment variable `DEBUG=1`.
- When using launchd, logs are written to `/var/log/socket_vmnet/stderr`.
`/var/log/socket_vmnet/stdout` is not used and expected to be empty.
- On Mac, make sure that the IDE (ie: vscode) have privileges on the "local network" in "System Settings" -> "Privacy & Security" -> "Local Network". Symptom: Execute bash script from VSCODE terminal (or any IDE), `socket_vmnet` start correctly, VM can ping its gateway (host bridge interface), VM can ping internet, VM can ping host but host can NOT ping VM.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • "On Mac" isn't meaningful here as Mac is the only supported host platform
  • The sentence should not assume that everybody is using IDE
  • "ie: vscode" sounds like vscode is the only IDE in the world. Did you mean "e.g., "?
  • vscode, VSCODE -> VS Code, or Visual Studio Code
  • "Symptom: ..." is grammatically hard to read as it starts with an imperative mood. You can ask @copilot to improve the sentence
  • What is the "bash script" here?

Copy link

Copilot AI Feb 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new troubleshooting bullet has several grammatical and style issues (e.g., subject-verb agreement, "ie" vs. "i.e.", and IDE name capitalization), which makes the guidance harder to read; consider rephrasing to something like: "On macOS, make sure that your IDE (e.g., VS Code) has permission for the Local Network in System Settings → Privacy & Security → Local Network. Symptom: when executing the bash script from the IDE terminal, socket_vmnet starts correctly, the VM can ping its gateway and the internet and the host, but the host cannot ping the VM."

Suggested change
- On Mac, make sure that the IDE (ie: vscode) have privileges on the "local network" in "System Settings" -> "Privacy & Security" -> "Local Network". Symptom: Execute bash script from VSCODE terminal (or any IDE), `socket_vmnet` start correctly, VM can ping its gateway (host bridge interface), VM can ping internet, VM can ping host but host can NOT ping VM.
- On macOS, make sure that your IDE (e.g., VS Code) has permission for the Local Network in System SettingsPrivacy & SecurityLocal Network. Symptom: when executing the bash script from the IDE terminal, `socket_vmnet` starts correctly, the VM can ping its gateway and the internet and the host, but the host cannot ping the VM.

Copilot uses AI. Check for mistakes.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot, see also my comment in #151 (comment)