I was looking into setting a static ip address for the machine's but im not entirely sure how we would go about that.
There are a few different ways to setup your network switch and would we implement different ways to set the ip address based on the network configuration?
Currently Vagrant doesnt manage the switches in any way, should we even try and start doing that.
When it is a extenal switch you basically part of the same network as the host, which usually means there is DHCP and a static IP is limited to your subnet. Also there is the possibility of collisions.
An internal switch has possiblities, but would require the user to share his internet on his adapter manually to get internet on the machine.
Another possibility is doing an internal switch and create a nat network, which would give some flexiblity, but i know that docker does this also and would probably conflict with that since windows can only handle one NAT network.
Anyways, i'm not entirely sure what the best way to go about it is.
I was looking into setting a static ip address for the machine's but im not entirely sure how we would go about that.
There are a few different ways to setup your network switch and would we implement different ways to set the ip address based on the network configuration?
Currently Vagrant doesnt manage the switches in any way, should we even try and start doing that.
When it is a extenal switch you basically part of the same network as the host, which usually means there is DHCP and a static IP is limited to your subnet. Also there is the possibility of collisions.
An internal switch has possiblities, but would require the user to share his internet on his adapter manually to get internet on the machine.
Another possibility is doing an internal switch and create a nat network, which would give some flexiblity, but i know that docker does this also and would probably conflict with that since windows can only handle one NAT network.
Anyways, i'm not entirely sure what the best way to go about it is.
Perhaps you have some insight @PatrickLang :)