You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run in both a ping to the 2nd computer on the local network.
--->> Ping works within iTerm2 but within VSCode returns "No route to host"
Pinging the gatway works in both cases. As does pinging something beyond the gateway e.g. public 1.1.1.1...
Does anyone know what causes this issue? I tried to compare the output of netstat -rn but it looks identical. What is going on here???
As #233846 was closed without the bug being solved I'm going to reopen this. I think that issue was labeled incorrectly by mistake as the label and automated response that caused it to be closed do not match the issue nor was a meaningful explanation provided.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.96.2. Please try upgrading to the latest version and checking whether this issue remains.
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Pinging the gatway works in both cases. As does pinging something beyond the gateway e.g. public 1.1.1.1...
Does anyone know what causes this issue? I tried to compare the output of
netstat -rn
but it looks identical. What is going on here???As #233846 was closed without the bug being solved I'm going to reopen this. I think that issue was labeled incorrectly by mistake as the label and automated response that caused it to be closed do not match the issue nor was a meaningful explanation provided.
The text was updated successfully, but these errors were encountered: