I'm having big problems with Vagrant lately:
- My private network's IP gets properly assigned (to eth1) on the first vagrant up - On the first vagrant reload, the IP is inappropriately assigned to eth0 (the regular NAT network nic), and the IP now shows on both eth0 and eth1 - On third vagrant reload, eth1 is disabled Upon the third vagrant reload, my project is trashed because I can't use the private network anymore. My project has a rather long initial vagrant up so it is very painful for my team to have to destroy frequently. I see lots of networking issues reported on GitHub, so I don't have much hope that this one will get fixed anytime soon, so I'm looking for any workarounds you might have. Here's a detail of my problem: https://github.com/hashicorp/vagrant/issues/9510#issuecomment-371560182 Thanks, Jamie -- 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/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2BqKrW-0WeKGiuQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
