-
-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface Error upon Vagrant Up #28
Comments
Hi @digital4rensics, Unfortunately I haven't seen this type of error before. Do you mind adding which OS, Vagrant, and VirtualBox versions you're using? |
Not a problem - This was on: |
Also noted that if I log in to the logger box - eth1 does seem to be configured, and I can hit the Splunk interface, but not the osquery one. |
So the odd part about this is that since Ubuntu 15 (I believe), network interfaces are no longer using the eth[#] naming scheme. You appear to be experiencing this Vagrant bug, which was supposed to be fixed in 1.9.3: hashicorp/vagrant#6871. Maybe there are some workarounds in that thread that might fix this for you. My output for logger is shown below.
|
Secondary note - I tried to bring each system up independently. I'll see if this functions w/ sysmon & splunk as is and perhaps try to work through the link you posted. Confirmed your output does differ from mine. Second Win10 Output: |
This morning, I killed everything w/ Vagrant and started over. I didn't attempt to bring the boxes up collectively this time, just did each individually. This round got a bit more running with a few less errors. IE: Fleet came up and is functioning and can see both WEF and WIN10. Did still get the Win10 errors posted above. |
Guys, I know ifconfig is deprecated but it helped me to change ifdown/ifup to ifconfig up/down in C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-2.0.1\plugins\guests\debian\cap\configure_networks.rb My vagrant version is 2.0.1 |
+1 this lab is amazing Same issue here though |
This is really bizarre. By all accounts, this is supposed to be fixed in Vagrant by now. I've been digging through this issue: hashicorp/vagrant#1777
After doing that, can you also go to |
Thanks that looked to have fixed it! Initially I wasn't seeing Splunk set up with providers or indexes (and I lost the log output, so I did a If anyone comes across this in the future, try to |
@digital4rensics can you give this fix a shot and let me know if it takes care of the issue for you? |
Hmm. After a suspend, logger does not come back up due to a port forwarding conflict. And after a halt and
So I scratched the image again and ran |
Yeah, it's some Vagrant weirdness I think. I'm usually able to solve it with You can check what's listening on the port with: I'm going to go ahead and close this issue out as it sounds like the Vagrant reinstall + deleting the old box fixed the original network interface issue. Feel free to open it back up if that issue reappears at some point. |
Reopening as I just ran into this issue for the first time tonight :) |
+1 for this issue. Running into both the interface issue, as well as the port forwarding issue. Using a fresh install of Ubuntu 16.04.1, Vagrant 2.0.1, and VirtualBox 5.2.4. I got around the interface issue by logging into the logger guest, running an ifconfig, and re-running I tried removing and reinstalling vagrant, but now stuck in a rabbit hole around "could not find gem vagrant-reload" so will work on that shortly. |
First, I just want to say thanks for releasing this lab. It's amazing work. Second, I am running into both of the issues mentioned here. I 'fixed' the interface issue by running |
I found the same, but it still seems like a temporary solution. After a virtualbox crash, it's now telling me 8001 is in use, so will need to increment again. |
Same thing for me, incremented again. |
Thank you for the reports. I’m considering removing the port forwarding completely due to seemingly poor support in Vagrant and the fact that it’s a bit redundant (you can access the same services by connecting directly to the host). If anyone has objections to that, please let me know. As for the interface issues, I’ll have to dig deeper to find the root cause. I’m on holiday until Jan 9, so it might be a bit before I’m able to work on a fix. Thanks again for all the kind words and reports and happy 2018! |
Makes sense to me. Ill be on the lookout for it. Enjoy the holiday and happy new year! |
Hey folks, Is anyone still experiencing this issue? I just pushed a pretty big change with some updates and am curious if this issue still exists. I'll wait a week or so for responses, but will be closing this out if there's no further comments. |
Closing due to lack of activity |
I ran into this after installing isc-dhcp-server on Ubuntu Server 18.04 LTS in combination with a public_network config using a static IP. |
Hi! First off - awesome work - the amount of time to get this sort of lab set up with be reduced significantly due to this effort.
For the error - is this something you've run across using Virtualbox? Everything up to this point completed without issue.
==> logger: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ifdown 'eth1' || true
/sbin/ip addr flush dev 'eth1'
Remove any previous network modifications from the interfaces file
sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre
sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post
cat
/tmp/vagrant-network-interfaces.pre
/tmp/vagrant-network-entry
/tmp/vagrant-network-interfaces.post \
rm -f /tmp/vagrant-network-interfaces.pre
rm -f /tmp/vagrant-network-entry
rm -f /tmp/vagrant-network-interfaces.post
/sbin/ifup 'eth1'
Stdout from the command:
Failed to bring up eth1.
Stderr from the command:
/sbin/ifdown: interface eth1 not configured
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
The text was updated successfully, but these errors were encountered: