Based on the work by wjordan in this comment
The solution is to force the update of RubyGems to side step the issue.
gem update --force --system 2.6.11
Then the error does not occur.
You must connect to your Cisco device from another machine using an earlier version of OpenSSH as the reason for this error is:
The solution is as follows:
You can actually get away with (for now) using Bitvise SSH on Windows and enabling the disabled Algorithms, etc. to allow you to connect to the Cisco device.
This mainly demonstrates my goal of preparing a Raspberry Pi to be provisioned prior to its first boot. To do this I have chosen to use the same cloud-init that is the standard for provisioning servers at Amazon EC2, Microsoft Azure, OpenStack, etc.
I found this to be quite challenging because there is little information available for using cloud-init without a cloud. So, this project also servers as a demonstration for anyone on any version of Linux who may want to install from source, and/or use without a cloud. If you fall into that later group, you probably just want to read the code. It's
bash so everything I do, you could also do at the command line. (Even the
|# Sampling of security headers|
|http-response set-header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"|
|http-response set-header X-Frame-Options SAMEORIGIN|
|http-response set-header X-XSS-Protection "1; mode=block"|
|http-response set-header Referrer-Policy no-referrer-when-downgrade|
Create the following file:
" This file loads the default vim options at the beginning and prevents " that they are being loaded again later. All other options that will be set, " are added, or overwrite the default settings. Add as many options as you " whish at the end of this file. " Load the defaults
Install ACMESharp as per here.
Follow the installation steps from the getting started guide before using the instructions below.
Run the following command to install the module:
TFTP is said to "only use UDP 69" but this is completely and totally inaccurate.
TFTP starts communications on UDP 69, then moves the conversation to ephemeral ports between the two systems-and depending on the systems involved, they can change during the boot process.
Note, this doesn't seem to work across VLANs....
So, where do you start?
Step 1) You need UDP 67, 69, 4011, 1024:5000 from your PXE booting machine to the PXE Server. This is because the PXE bootloader appears to use that range specifically.
Netplan seems to not play nicely with VLANs (or so it would appear), further testing required
systemd-resolve issues, solution