Copy from a tftp to a stack master
copy tftp://192.168.0.8/powerconnect_35xx-20066.ros image
Create the following file: /etc/vim/vimrc.local
" 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
Why, that's simple! Copy this script to your USG, run chmod +x on it and then, as a user with sudo permission, execute it.
Shamelessly borrowed from Brittanic on the Ubiquiti Unifi forums
Simply run the following command (note, if you are at all security concious-don't run it and instead review the script, then copy it to your USG to execute).
curl https://gist.githubusercontent.com/troyfontaine/7e6f93e32621177fc9a94e823adc52b5/raw/fix_ddns.sh | sudo bash
#!/bin/bash | |
# Create fullchain | |
cat ~/cert/*.ca-bundle ~/cert/*.crt >> fullchain.cer | |
# Generate pkcs12 cert from acme output | |
openssl pkcs12 -export -in ~/cert/fullchain.cer -inkey \ | |
~/cert/mydomain.key \ | |
-out ~/cert/unifi.p12 -name unifi -password pass:aircontrolenterprise | |
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 for
loop.)
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.
Requirements:
This document is written for Unifi Controller Software v5. Configuring the Unifi Controller Guest Network, the Hotspot Portal and SSL is actually fairly involved and requires modifying the configuration in several locations-as well as adding the SSL certificate via SSH. So this will consist of several discrete procedures to achieve the end goal.
This document provides some basic guidance on how to customize the Unifi Controller v5.6+ Hot Spot Portal feature. Existing documentation seems to be scarce in this technician's opinion.
This readme is the culmination of some exploration in customizing the portal for business use. Please note, all examples use the installed location of the Unifi v5 Controller software on the Unifi CloudKey.
Some issues have been encountered after upgrading the Unifi Controller to newer releases specifically with the Hot Spot Portal customizations on Unifi Controller versions greater than 5.10 relating to the use of these instructions. You may not have a choice but to upgrade your included default template to the latest version and re-modify your portal files.
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:
Install-Module ACMESharp.Providers.CloudFlare