Log in to the edgeLinux OS and Antlets

Access the edgeLinux OS terminal

There are several ways you can access the edgeLinux OS terminal

  • In AntMan (vers. 0.9.1)

  • via SSH

  • Connect a keyboard and monitor

  • IPMI: see the setup page Click the '>_Console' link in the main menu.

Antman
SSH
Antman

Prior to antMan 0.10.0 You are prompted to enter your root username.

Now you have access to the EdgeLinux command line.

SSH

You can SSH to the edgeLinux OS in the following ways

Using the private IP address of the antsle

Using antsle_name.local

replace 'myantsle' with the name of your antsle

With an .antsle.us subdomain

You can get an antsle.us subdomain in antHill

Access antlets via ssh

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

Access antlets from the edgeLinux terminal

Just login to Antsle's command line as shown above, then open a new SSH session into your antlet. e.g. antlet has IP address 10.1.1.12

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.

In this example we not required to include the username 'root' because, if omitted, SSH will use the name of the currently logged in user. The terminal prompt shows that 'root' is currently logged in.

Via the edgeLinux forwarding on port 22xxx

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 IP 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

Via the IP address of a bridged NIC

If you have configured a bridged virtual NIC on an antlet you can SSH directly to the IP address of the bridged interface.

SSH Tools

In case you are not familiar with ssh, it's very easy to use with many excellent tutorials out there.

MacOS and Linux: SSH is built-in and run with the terminal Windows: For Windows you can use packages like PuTTY or MobaXterm.

Or try WSL, aka: Bash on Ubuntu on Windows. This seems to work well but will not resolve .local domain names.

Caveats

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.

If the ssh or sftp connection to an antlet is not working via port 22xxx, try running the command 'portmappings' from the edgeLinux command line. This will make sure the ssh and rdp port mappings are in place.

RDP access

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:

Field

Example antlet 10.1.1.33

antlet 10.1.1.{num}

PC Name

myantsle.local:3033

myantsle.local:3000+{num}

User name (Windows Server)

Administrator

User name (Windows 10)

antsle

Password

antsleWin12

if you configured a bridged virtual NIC, the following method will not work. You can RDP directly to the IP address configured on the bridged interface. (WIP)

If the rdp connection to an antlet is not working, try running the command 'portmappings' from the edgeLinux command line. This will make sure the ssh and rdp port mappings are in place.

Web access to your antlets

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.

To make the web apps installed in your antlets accessible, edgeLinux provides a reverse proxy using a software package called nginx.

See how easy it is to get web access to your antlets: