View Issue Details

IDProjectCategoryView StatusLast Update
0005046Kali Linux[All Projects] General Bugpublic2018-10-29 19:03
Reportern3d.b0y Assigned Tosteev  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionno change required 
Product Version2018.3 
Target VersionFixed in Version 
Summary0005046: Vagrant box Error
DescriptionIf you deploy a package with the parameter vb.gui = false. Then it hangs on stage "default: SSH auth method: private key". I would really like you to solve this problem.

Activities

steev

2018-10-21 19:04

developer   ~0009822

Please don't set the resolution to not fixable, if it actually is fixable.

Have you tried building the vagrant box yourself, following the headless instructions in the github readme? Are you able to set vb.gui = false then?

n3d.b0y

2018-10-21 20:28

reporter  

log (1,831 bytes)
==> default: Importing base box 'offensive-security/kali-linux'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'offensive-security/kali-linux' is up to date...
==> default: Setting the name of the VM: Pentest_default_1540153133159_68673
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2201
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (5.2.18) correctly, but not running.
Failed to start vboxadd.service: Unit vboxadd.service not found.
Failed to start vboxadd-service.service: Unit vboxadd-service.service not found.
bash: line 4: setup: command not found
==> default: Checking for guest additions in VM...
==> default: [vagrant-hostsupdater] Checking for host entries
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

 setup

Stdout from the command:



Stderr from the command:

bash: line 4: setup: command not found
log (1,831 bytes)

n3d.b0y

2018-10-21 20:28

reporter  

Vagrantfile (317 bytes)
Vagrant.configure("2") do |config|
  config.vm.box = "offensive-security/kali-linux"
  config.vm.box_version = "2018.3.1"

  config.vm.provider "virtualbox" do |vb|
	vb.gui = false
	vb.memory = "4096"
  end

  config.vm.provision "shell", inline: <<-SHELL
    apt-get update
    apt-get install -y crowbar
  SHELL
end
Vagrantfile (317 bytes)

n3d.b0y

2018-10-22 17:12

reporter   ~0009825

I do not understand you

steev

2018-10-23 05:39

developer   ~0009829

We can't seem to reproduce the issue here:

==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /Users/steev/vagrant-boxes/kali-bug
==> default: Running provisioner: shell...
...SNIP...


What is the host system that you are trying to run this on?

n3d.b0y

2018-10-24 09:16

reporter   ~0009833

The issue is happened because I added *config.vm.network “public_network”, bridge: “en0: Wi-Fi (AirPort)“* in the vagrant file. That’s why he freeze during the *SSH auth method: private key*. How can I add network bridge? It is important for me, because the main issue in Wardriving.

steev

2018-10-29 19:03

developer   ~0009843

You can't use the en0 driver for wardriving, only usb wifi devices will work. Vagrant is still limited by VirtualBox limitations. I don't believe this is a bug, but a configuration issue. If you need assistance setting that up, you should post to the forums. https://forums.kali.org

Issue History

Date Modified Username Field Change
2018-10-21 18:26 n3d.b0y New Issue
2018-10-21 18:26 n3d.b0y Resolution open => not fixable
2018-10-21 19:00 steev Resolution not fixable => open
2018-10-21 19:04 steev Note Added: 0009822
2018-10-21 20:28 n3d.b0y File Added: log
2018-10-21 20:28 n3d.b0y File Added: Vagrantfile
2018-10-22 17:12 n3d.b0y Note Added: 0009825
2018-10-23 05:39 steev Note Added: 0009829
2018-10-24 09:16 n3d.b0y Note Added: 0009833
2018-10-29 19:03 steev Assigned To => steev
2018-10-29 19:03 steev Status new => resolved
2018-10-29 19:03 steev Resolution open => no change required
2018-10-29 19:03 steev Note Added: 0009843