hello Vagrant currently is hard coded on first interface to traditional NAT for Virtualbox.
Options at the moment are add private_network, and set hostnames. If there is not an open issue for this, could you open one on github and share some words on how this would be beneficial ? Thanks Alvaro On Tue, Sep 27, 2016 at 4:38 AM, Andy Wang <[email protected]> wrote: > hi, have you found solution for this issue ? I came across same issue when > I try to setup two guest VM which can communicate each other . > > andy > > On Wednesday, May 20, 2015 at 4:21:42 AM UTC+8, Chris Almond wrote: >> >> Can anyone share examples that show how to specify use of the new "NAT >> Network" option for network type? >> >> Virtualbox doc ref: *6.4. Network Address Translation Service >> (experimental)* https://www.virtualbox.org/man >> ual/ch06.html#network_nat_service >> >> The goal is to use Vagrant to provision a cluster of boxes, all members >> of the same custom defined NAT service, with DHCP providing address within >> a set range for that NAT segment. >> >> Is this possible via vagrant? In my (minimal) research and >> experimentation with Vagrant so far I'm finding that I need to use the new >> NAT service type for this setup (instead of standard "NAT"). >> >> Learn how WANdisco Fusion solves Hadoop data protection and scalability >> challenges <http://www.wandisco.com/hadoop/wd-fusion> >> >> Listed on the London Stock Exchange: WAND >> <http://www.bloomberg.com/quote/WAND:LN> >> >> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY >> BE PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its >> subsidiaries, ("WANdisco") does not waive any confidentiality or >> privilege. If you are not the intended recipient, please notify us >> immediately and destroy the message without disclosing its contents to >> anyone. Any distribution, use or copying of this e-mail or the information >> it contains by other than an intended recipient is unauthorized. The views >> and opinions expressed in this e-mail message are the author's own and may >> not reflect the views and opinions of WANdisco, unless the author is >> authorized by WANdisco to express such views or opinions on its behalf. >> All email sent to or from this address is subject to electronic storage and >> review by WANdisco. Although WANdisco operates anti-virus programs, it >> does not accept responsibility for any damage whatsoever caused by viruses >> being passed. >> > -- > 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/79cbe2a0-561f-47d7-a547-5c913bb1468f%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/79cbe2a0-561f-47d7-a547-5c913bb1468f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eygPR%3DxDJARpbc095cJWUB0kpJR5UqP-an8fUQ-SmAhqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
