I have reasons for not wanting to use DHCP in this situation. And the Vagrant doc which you mentioned, and which I had already read, does not provide a way to differentiate between specifying an IPv4 address versus an IPv6 address. The config.vm.network directives are identical which suggests there may be no way to do this.
On Tuesday, May 10, 2016 at 2:20:25 PM UTC-7, Alvaro Miranda Aguilera wrote: > > Hello, > > The easiest way is use bridge and let the dhcp/dhcpv6 to take care: > https://www.vagrantup.com/docs/networking/public_network.html > > Or you can create 2 networks, one for ipv4 other for ipv6 and set the ip > like this: > https://www.vagrantup.com/docs/networking/private_network.html > > Alvaro. > > On Wed, May 11, 2016 at 8:05 AM, Robert F <[email protected] > <javascript:>> wrote: > >> I should have mentioned that I'm running Vagrant on a Mac, not Windows. >> Yes, if you have any examples of how this is done, I would love to see them. >> >> On Tuesday, May 10, 2016 at 12:39:43 PM UTC-7, Robert F wrote: >>> >>> Is it possible to create a private network on a Vagrant box that has >>> both an IPv4 and IPv6 address? I'd like to do something like this: >>> >>> config.vm.network "private network", ip: "192.168.1.100" >>> config.vm.network "private network", ip6: "<some internal private IPv6 >>> address>" >>> >>> The reason I'd like to do this is that I have an Ansible play that needs >>> to reference "ansible_default_ipv6.address" but there is no such address >>> associated with my Vagrant VM if I'm also using an IPv4 address. The >>> Vagrant documentation doesn't discuss this so I'm guessing its not possible >>> but I thought I would check here in case there's some undocumented way to >>> do it. >>> >>> Thanks! >>> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/484eca69-6808-4c70-a2bb-17c3e0299699%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/484eca69-6808-4c70-a2bb-17c3e0299699%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/0dd868c5-45ac-47e0-b175-295695156ff2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
