Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53410 - [vagrant] requires net-tools as dependency

Attached to Project: Community Packages
Opened by Joonas Hämäläinen (joonas) - Wednesday, 22 March 2017, 09:40 GMT
Last edited by Jonathan Steel (jsteel) - Thursday, 30 March 2017, 10:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Vagrant needs net-tools as dependency so it can create routing for guests. Starting new vagrant environments without net-tools installed doesn't give any error. Also port forwarding through localhost works as intented. Problems arise when wanting to use vagrant machines assigned IP address directly.

Additional info:
* package version(s):
community/vagrant 1.9.2-1

Steps to reproduce:
1. Have fresh arch installation, without net-tools installed.
2. Install vagrant, virtualbox et all.
3. Download any box (for example https://github.com/rlerdorf/php7dev.git )
4. vagrant up
5. 127.0.0.1:8000 works, but 192.168.7.7 doesn't

Install net-tools, halt vagrant and vagrant up again, now 192.168.7.7 works as intented.
This task depends upon

Closed by  Jonathan Steel (jsteel)
Thursday, 30 March 2017, 10:39 GMT
Reason for closing:  Not a bug
Comment by Jonathan Steel (jsteel) - Thursday, 30 March 2017, 08:34 GMT
When you installed virtualbox you should have seen:

Optional Deps : net-tools: Host-only or bridged networking support

Vagrant doesn't create the route on the host to the guest network; Virtualbox does.
Comment by Joonas Hämäläinen (joonas) - Thursday, 30 March 2017, 09:13 GMT
Now that you pointed that out, it makes more sense, and I find information which states it needs to be installed separately. So this isn't bug, just user error who didn't know where to look in first place.
Comment by Jonathan Steel (jsteel) - Thursday, 30 March 2017, 10:38 GMT
OK great. No problem. I'll close this now.

Loading...