David, Not sure if this will work in your exact situation, but many of us use this script [1] to set up proxies with internal IP addresses. So if your VM had an IP of 192.168.121.12 you would go to <hypervisor_hostname>:50012 and you can access your VM. I am not sure if this can be tweaked for bridged networking, but figured I would share.
[1] https://gist.github.com/johnpmitsch/a69c904d9af358834907427fa697edbe John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Wed, Sep 7, 2016 at 1:21 PM, David Davis <[email protected]> wrote: > Is anyone connecting to their vagrant VMs directly from another machine, > one other than the box running vagrant? I have a desktop I am using to spin > up vagrant VMs but I do most of my work on my laptop. > > Currently, I am using bridged networking on the hypervisor to give the VM > a network IP that I can access directly. However, provisioning from my dev > environment doesn’t seem to work and some of the playbooks in forklift that > involve one VM connecting to another don’t seem to work either. > > I know I could also forward ports using my desktop’s firewall but having > to add those rules every time I spin up a VM doesn’t seem ideal. Are there > any other options I am missing? > > Thanks. > > David > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
