There is an action going on regarding this issue. Please, find the explanation in some details here:
[Former issue #9426] Assigning private network to ETH2 interface got magically assigned to the ETH1 interface?! #9510 https://github.com/hashicorp/vagrant/issues/9510 Private network IP assigned to wrong interface on vagrant reload #9546 https://github.com/hashicorp/vagrant/issues/9546 Thank you, Zoran _______ On Friday, February 2, 2018 at 6:09:47 AM UTC+1, _nobody_ _nobody_ wrote: > > This is the perfect answer (which I knew already/yesterday I got the more > complete idea - the domain I am in is not so trivial). The only problem > here: I do NOT see/envision anywhere in such /bin/bash script > Vagrant/Vagrant environment?! > > We are talking here about Vagrant networking, ain't/aren't we??? > > Thank you, > Zoran > > -- 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/dc201619-0b03-43af-831b-387256477615%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
