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
With the move to M1 laptops, virtualbox is unusable... but we are hitting an issue with the vpn client intercepting any connection to anything else than 127.0.0.1 when using parallels and its default direct ssh connection to the vm ip... Therefore, as of today, the only way we can use parallels, ssh and vagrant is via manual port forwarding and forcing
This works fine as long as you only run a single vm... but port collision support would really make our life easier when running more than one vm... We are using the version 2.3.1 of the plugin... Can the old restriction linked to version < 10 be removed so that we can use Parallels via localhost port forwarding (like VirtualBox behavior)
The text was updated successfully, but these errors were encountered:
With the move to M1 laptops, virtualbox is unusable... but we are hitting an issue with the vpn client intercepting any connection to anything else than 127.0.0.1 when using parallels and its default direct ssh connection to the vm ip... Therefore, as of today, the only way we can use parallels, ssh and vagrant is via manual port forwarding and forcing
This works fine as long as you only run a single vm... but port collision support would really make our life easier when running more than one vm... We are using the version 2.3.1 of the plugin... Can the old restriction linked to version < 10 be removed so that we can use Parallels via localhost port forwarding (like VirtualBox behavior)
The text was updated successfully, but these errors were encountered: