Vagrant builtin ssh (at `vagrant up`) still problems with key exchange

pmhausen · March 8, 2022, 11:03am

Hi all,

can anybody advise me on how to draw some attention to this issue?

vagrant up still cannot connect via ssh on initial startup. vagrant ssh works fine.

opened 10:43PM - 13 Feb 22 UTC

### Vagrant version $ vagrant -v Vagrant 2.2.19 ### Host operating system… MacOS Monterey 12.2.1 ### Guest operating system FreeBSD 13.0-p7 (OPNsense) ### Vagrantfile This Vagrantfile downloads a standard FreeBSD 13.0 box and on initial provisioning turns it into an OPNsense firewall. In the process OPNsense replaces the FreeBSD bundled sshd with OpenSSH_8.8p1 from ports. Initial provisioning works, after that subsequent `vagrant up` commands fail because the builtin ruby SSH cannot authenticate. `vagrant ssh` works. I need `vagrant up` to work, because without the NFS mount I won't have my development environment available in the box. My project can be found on github: https://github.com/punktDe/vagrant-opnsense ```ruby Vagrant.configure(2) do |config| # Which base box to use - this is FreeBSD 12.1 for now according to # https://github.com/opnsense/update $opnsense_box = 'punktde/freebsd-130-ufs' # Which OPNsense release to install $opnsense_release = '22.1' # IP address of the firewall in the host-only network $virtual_machine_ip = '192.168.1.1' # Configure folder sharing $vagrant_mount_path = '/var/vagrant' config.vm.synced_folder '.', '/vagrant', id: 'vagrant-root', disabled: true config.vm.synced_folder '.', "#{$vagrant_mount_path}", :nfs => true, :nfs_version => 3 # Enable SSH keepalive to work around https://github.com/hashicorp/vagrant/issues/516 config.ssh.keep_alive = true # Configure proper shell for FreeBSD config.ssh.shell = '/bin/sh' # Every Vagrant development environment requires a box. You can search for # boxes at https://atlas.hashicorp.com/search config.vm.box = $opnsense_box # Create a private network, which allows host-only access to the machine # using a specific IP config.vm.network 'private_network', ip: $virtual_machine_ip, auto_config: true # Customize build VB settings config.vm.provider 'virtualbox' do |vb| vb.memory = 4096 vb.cpus = 1 end # Transfer config file snippets into VM config.vm.provision "file", source: "files", destination: "files" # Bootstrap OPNsense config.vm.provision 'shell', inline: <<-SHELL # Download the OPNsense bootstrap script fetch -o opnsense-bootstrap.sh https://raw.githubusercontent.com/opnsense/update/master/src/bootstrap/opnsense-bootstrap.sh.in # Remove reboot command from bootstrap script sed -i '' -e '/reboot$/d' opnsense-bootstrap.sh # Start bootstrap sh ./opnsense-bootstrap.sh -r #{$opnsense_release} -y # Set correct interface names so OPNsense's order matches Vagrant's sed -i '' -e 's/mismatch0/em1/' /usr/local/etc/config.xml sed -i '' -e 's/mismatch1/em0/' /usr/local/etc/config.xml # Remove IPv6 configuration from WAN sed -i '' -e '/<ipaddrv6>dhcp6<\\/ipaddrv6>/d' /usr/local/etc/config.xml # Remove IPv6 configuration from LAN sed -i '' -e '/<ipaddrv6>track6<\\/ipaddrv6>/d' /usr/local/etc/config.xml sed -i '' -e '/<subnetv6>64<\\/subnetv6>/d' /usr/local/etc/config.xml sed -i '' -e '/<track6-interface>wan<\\/track6-interface>/d' /usr/local/etc/config.xml sed -i '' -e '/<track6-prefix-id>0<\\/track6-prefix-id>/d' /usr/local/etc/config.xml # Enable SSH by default sed -i '' -e '/<group>admins<\\/group>/r files/ssh.xml' /usr/local/etc/config.xml # Allow SSH on all interfaces sed -i '' -e '/<filter>/r files/filter.xml' /usr/local/etc/config.xml # Do not block private networks on WAN sed -i '' -e '/<blockpriv>1<\\/blockpriv>/d' /usr/local/etc/config.xml # Create XML config for Vagrant user key=$(b64encode -r dummy <.ssh/authorized_keys | tr -d '\n') echo " <authorizedkeys>${key}</authorizedkeys>" >files/vagrant2.xml cat files/vagrant[123].xml >files/vagrant.xml # Add Vagrant user - OPNsense style sed -i '' -e '/<\\/member>/r files/admins.xml' /usr/local/etc/config.xml sed -i '' -e '/<\\/user>/r files/vagrant.xml' /usr/local/etc/config.xml # Change home directory to group nobody chgrp -R nobody /usr/home/vagrant # Change sudoers file to reference user instead of group sed -i '' -e 's/^%//' /usr/local/etc/sudoers.d/vagrant # Reboot the system shutdown -r now SHELL end ``` ### Debug output https://gist.github.com/pmhausen/d6bec5a244ac6332ed2ddeee888f3586 ### Expected behavior `vagrant up` should work. ### Actual behavior ``` ==> default: Booting VM... ==> 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: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... ... ``` ### Steps to reproduce 1. Provision an OPNsense in Vagrant with my project. 2. After initial provisioning and reboot: `vagrant halt` 3. `vagrant up` ### References - https://github.com/hashicorp/vagrant/issues/12344 - https://github.com/hashicorp/vagrant/issues/12418

As far as I can tell I followed the instructions including providing the complete debug output etc.

I cannot work on OPNsense topics, because Vagrant is completely dysfunctional for me.

Short summary: FreeBSD guest, current OpenSSH server from ports, Vagrant up cannot connect into the VM.

Thanks in advance,
Patrick

Topic		Replies	Views
Vagrant up error on Ubuntu 22.04: pkeys are immutable on OpenSSL 3.0 Vagrant	6	5583	May 19, 2022
SSH only works on first vagrant up; reboot times out ssh Vagrant	3	2266	September 2, 2023
SSH connection issue when vagrant up Vagrant	0	760	September 21, 2023
FreeBSD 14 and Fedora 39 not being correctly configured for ssh access Vagrant	0	55	June 19, 2024
Git upgrade created issue - vagrant ssh - terminating, 2 bad configuration options Vagrant	0	563	November 16, 2021

Vagrant builtin ssh (at `vagrant up`) still problems with key exchange

Related topics