Feb 4, 2015

Level 1

Homestead up - The specified host network collides with a non-hostonly network!

I already have VirtualBox installed and use it for a Windows VM I require for work. I've got that using two network adaptors: NAT and Bridged.

Following the guides and the VM instructions, I've installed Homestead no problem and got everything up to date. When I run "homestead up", it creates the VM instance but falls over at:

The specified host network collides with a non-hostonly network! This will cause your specified IP to be inaccessible. Please change the IP or name of your host only network so that it no longer matches that of a bridged or non-hostonly network.

I understand from the error (and comments on other parts of the web I've found) that there is a network conflict here. What I don't understand is how the hell do I fix it?!

Anyone any suggestions?

bashy

11 years ago

Level 65

Question is, is the IP the same for both VMs? Can you not just change it to something other than 192.168.10.10?

1 like

tadywankenobi

11 years ago

Level 1

I don't really understand what that means? I've looked through the VirtualBox interface and can't find a way to change the VM's IP address. I don't mind what IP it's on as long as it works! I tried changing the IP address to random different numbers in the Homestead.yaml, but no joy, still got the same error.

Any suggestions?

tadywankenobi

11 years ago

Level 1

Am I correct in understanding that the IP address in the Homestead.yaml file should be the IP address of my machine? So my machine here is 192.168.1.66, so that's what it should be set to?

tadywankenobi

11 years ago

Best Answer

Level 1

Ok, I don't really know why, but anything in the 192.168.1.* range wasn't working. I changed the IP completely to 10.1.1.33 and box is up now. I don't really understand it, but hey, if it's working...!

2 likes

bashy

11 years ago

Level 65

Yes, inside the .yaml file it sets it at the top. To host multiple VMs, that will need to be different. Haven't tried it with Homestead but I can confirm you can have multiple with different IPs.

You can go up 1 or 100, doesn't really matter. 192.168.10.11 or 192.168.10.100

1 like

santi

11 years ago

Level 1

I wanted my homestead guest machine to be in the same network than my host machine so I could access any site/domain in homestead from any machine or device in the same local network really easy.

My host machine IP: 192.168.1.2

My homestead desired IP: 192.168.1.200

Changing the following homestead setting in ~/.composer/vendor/laravel/homestead/scripts/homestead.rb did the trick :

    #config.vm.network :private_network, ip: settings["ip"] ||= "192.168.10.10"
    config.vm.network "public_network", :bridge => "en0: Wi-Fi (Airport)", :ip => "192.168.1.200"

2 likes

humpback

10 years ago

Level 1

Hi, where can I find this file ~/.composer/vendor/laravel/homestead/scripts/homestead.rb ?

bobbybouwmann

10 years ago

Level 88

@humpback Please create your own thread for different questions.... I almost missed your question...!!

Now that file is probably on your local machine. So you can use the command line to get to that file

humpback

10 years ago

Level 1

Sorry @bobbybouwmann just getting started with Laravel :) lots of confusion. Will open my own thread. Thank you

depsimon

10 years ago

Level 16

Here's another solution that does not require you to edit any file other than Homestead.yml.

Open VirtualBox, Go to Preferences > Network. Open the "Host-only Networks" and double click on the correct entry (mine is called vboxnet0). Open the DHCP Server tab and look for the "Lower Address Bound" and "Upper Address Bound". In my case it's 192.168.56.101 and 192.168.56.254.

Now you just have to use an IP between these bounds like 192.168.57.102 and use this IP in your Homestead.yml and try to vagrant up again.

Source & Video (in Spanish) : https://www.youtube.com/watch?v=XWushiLBgbw

3 likes