There are several ways you can access the edgeLinux OS terminal
In AntMan (vers. 0.9.1)
Connect a keyboard and monitor
IPMI: see the setup page Click the '>_Console' link in the main menu.
Prior to antMan 0.10.0 You are prompted to enter your root username.
Now you have access to the EdgeLinux command line.
You can SSH to the edgeLinux OS in the following ways
Using the private IP address of the antsle
replace 'myantsle' with the name of your antsle
With an .antsle.us subdomain
Use ssh to access your antlets to install and configure the software packages of your choice. Doing so is quick and easy.
The SSH command can be run from your terminal
ssh [email protected]_address
'username' is the user name for the antlet. The default username for all of our Linux templates is 'root', with the exception of the Ubuntu KVM template which has a default username 'ubuntu'. See the Templates/Passwords page.
The IP address can be the the actual IP address or a domain name that will resolve to the correct IP address.
There are several ways you can SSH to your antlets
From the edgeLinux terminal
Direct to the antlet
Via the edgeLinux forwarding on port 22xxx
Via the IP address of a bridged NIC
Just login to Antsle as shown above, then ssh into your antlet e.g. antlet has IP address 10.1.1.12
Here's how you can access your antlet directly, without the need to log in to Antsle first: In this scenario the username is still the username for the antlet, but the IP address is the that of the Antsle.
ssh -p 22012 [email protected]
The Antsle will forward to the correct antlet based on the port number. The port number is constructed by adding the last number in the IP address to 22000. In our example the antlet IP is 10.1.1.12 so the port number is 22012
If you have configured a bridged virtual NIC on an antlet you can SSH directly to the IP address of the bridged interface.
In case you are not familiar with
ssh, it's very easy to use with many excellent tutorials out there.
Or try WSL, aka: Bash on Ubuntu on Windows. This seems to work well but will not resolve .local domain names.
Ubuntu 16.04 KVM template:
Remember the Ubuntu KVM template has a default username: 'ubuntu'.
Port 22xxx does not work 1. If a bridged vNIC is configured on an antlet, port 22xxx will not work. But you can SSH directly to the address of the vNIC. 2. Port 22xxx only works on br0. If connected to a port other than br0, port 22xxx will not work. 3. Using antslename.local may not work if you have multiple interfaces (br0..br3) enabled and connected to the same network. In this case use the IP address of br0.
To access a Windows antlet with IP address 10.1.1.33 via RDP, use these credentials in your RDP client such as Microsoft Remote Desktop:
Example antlet 10.1.1.33
User name (Windows Server)
User name (Windows 10)
After having logged in via ssh, install all the software you want. Use package managers such as apt-get in debian or Ubuntu, yum in CentOS or Fedora, or pkg in FreeBSD to install your software. To get started, you might try this guide or this one.
See how easy it is to get web access to your antlets: