On a standard Vagrant VM, you'll see a NAT'ed interface with IP 10.2.0.15 and SSH listening on port 22 (inside the VM) and typically forwarded to port 2222 (for the host). Typically to access the Vagrant VM you just type 'vagrant ssh' and it's the equivalent of 'ssh -i ~/.vagrant/insecure_private_key -p 2222 [email protected]'.
It seems that you've defined your VM with a private network interface and decided that ssh should listen to that address instead? I.e. 192.168.121.82:22 When you do that, I believe, only connections "on the same subnet, i.e. 192.168.121.X, will be permitted to establish an ssh connection. You won't be able to connect from your host. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/14fb02f7-51a0-4728-abd2-756d11276774%40googlegroups.com.
