hello vagrant will do what you tell vagrant to do and will be limited to what your user can do.
Vagrant networking is very basic and cover the most general user cases, not all the features that are new into virtualbox are present in vagrant (read as features that have been created after the vagrant virtualbox provider was done) so if you think some of the features are useful, you can try to get them working on Vagrant and sumbit a Pull Request If you use private_networking, and use the same network on all the boxes, all of them will be connected to the same virtualbox network (like a switch) and you should be able to use . vm_ip:80 or vm_ip:443 Alvaro. On Tue, Mar 6, 2018 at 4:28 AM, Christian Gagneraud <chg...@gmail.com> wrote: > On 5 March 2018 at 08:29, Alvaro Miranda Aguilera <kiki...@gmail.com> > wrote: > > hello > > > > whats wrong on using a virtualbox box switch for this? > > > > since in the way you are doing it today i am not sure you will find more > > people using it or having the same issues > > I couldn't get it working with "plain" VBox network, i tried vagrant's > "public_network", "private_network" or using the "--intnet" trick. > I could have use the forwarded_port, unfortunately to listen on > 1.2.3.4:80 and 1.2.3.4:443 I would have to run the VM as root. > So I had no choice but to use port forwarding. > > What i've recently discovered is that my problem has actually a name: > "Hairpin NAT" > And there's a possible alternative (what i'm using right now): > Split-horizon DNS" > > You can find details at https://serverfault.com/a/557776 > > I'm still interested to know if I can use Vagrant to have this > scenario working, or if the problem is purely on VBox side (which I > believe is) > > Thanks, > Chris > > -- > 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 vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/CABxGUTjTCz8L2mdN9SvN51Mg1SVYb9f9DDRJ8e7sOwX%3Do7rKXQ% > 40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- 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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez0hNrGRZGmcpDfYQM7YCPsrHrqeucr1b3RtzHEetnuPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
