Homestead requires net-tools package for IP access to work.

[david-polak]

Versions

Vagrant 1.9.2
VirtualBox Version 5.1.18 r114002
Homestead HEAD detached at v5.1.0

Host operating system

Arch Linux 4.10.6-1-ARCH

Homestead.yaml

ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/Data/Code/laravel
      to: /home/vagrant/laravel

sites:
    - map: photshr.app
      to: /home/vagrant/laravel/photshr/public

databases:
    - photshr

/etc/hosts

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost
::1		localhost.localdomain	localhost
127.0.0.1	dntb.localdomain	dntb

192.168.10.10  	photshr.app

Expected behavior

photoshr.app should be accessible by ping or http

Actual behavior

photoshr.app was not accessible. Fixed by installing deprecated net-tools package.

Steps to reproduce

1. Remove net-tools package
2. vagrant destroy
3. vagrant up

[svpernova09]

I don't think this is a Homestead issue, this is an issue that your Host Operating System is missing networking packages.

[david-polak]

It depends on net-tools which was deprecated and is unmaintained for 7 years now. I don't know how much longer will distributions continue supplying it in the repositories. At least it would be good to mention the dependency in docs.

Or should I post this somewhere else? Vagrant perhaps? Not really sure about where to put this...

[raulpegan]

Arch Linux has the option to install net-tools. But as David said, relying on deprecated software is a bad idea, regardless of what the host operating system is.

[ali-wells]

I think this should be re-opened, this one had me at a standstill for a couple of days when I was getting Homestead setup on a Ubuntu 17 install.

[svpernova09]

So it looks like there's some issues on the Vagrant repo that may provide some light into the issue.

• Vagrant guest and host cannot communicate (Ubuntu 17.04)  hashicorp/vagrant#8626
• Can't reach private network on Debian 9 (stretch) host hashicorp/vagrant#8686

Seem to be a similar issue but solved with "just install net-tools".

• Use ip instead of deprecated ifconfig for Red Hat/CentOS guests hashicorp/vagrant#7460

Is a similar issue (I believe), but they're only aware of it on Cent/RH.

• Default route not set properly when :use_dhcp_assigned_default_route => true; net-tools not present in Debian stretch hashicorp/vagrant#8730

References the Cent/RH issue but point out Debian is having the same issues as Cent/RH.

It sounds like Vagrant needs to completely deprecate the need for net-tools and switch to whatever the replacement is. It also sounds like this may be underway.

Taking all of this into account, there is nothing we can do here at the Homestead level. We can only support the operating systems that Vagrant (and our other dependencies such as Virtualbox, etc) requires. "Just install net-tools" isn't an answer I'm happy about, but it seems to be the answer Vagrant is content with at the moment.

Now if you're using an operating system that has completely removed support for net-tools and you're trying to use an application that depends on it, you're not using a supported operating system and therefore will likely run into issues. The resolution here is "use a supported operating system".