Timeline for vagrant on windows 10 incorrect network configuration on multi-machine setup
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2020 at 16:18 | vote | accept | danidar | ||
| Jun 7, 2020 at 16:17 | comment | added | danidar |
why vagrant sets eth0 on all the machines deployed to the same IP 10.0.2.15? I found a workaround and not configuring the private network in the vagrantfile to the same range as the nat network allows the machines to be reacheable. so doing this; ldap.vm.network "private_network", ip: "192.168.2.100" works
|
|
| Jun 7, 2020 at 12:55 | history | edited | Pierre.Vriens♦ | CC BY-SA 4.0 |
added 4 characters in body
|
| Jun 4, 2020 at 12:16 | history | edited | anVzdGFub3RoZXJodW1hbg | CC BY-SA 4.0 |
added 83 characters in body
|
| Jun 4, 2020 at 11:41 | history | edited | anVzdGFub3RoZXJodW1hbg | CC BY-SA 4.0 |
added 217 characters in body
|
| Jun 4, 2020 at 11:33 | history | answered | anVzdGFub3RoZXJodW1hbg | CC BY-SA 4.0 |