Getting Started Using Our App

This guide will help you understand the basics for setting up and deploying the Eternal N Access Server

Eternal N Access Server consists of three major components:

    1. Eternal Server
    2. Admin Web Interface/Admin UI
    3. Connect Client

Eternal N Server: 
The N server is the underlying component in Eternal N Access Server that does all of the background work; routing, tunneling, encryption, user management, authentication etc. Eternal N Access Server comes with a Web GUI that helps to manage the underlying components of the N server.

Admin Web Interface: 
The Admin Web Interface makes for an easier management interface in Eternal N Access Server. In the Admin Web Interface an administrator can manage options such as layer 2 or layer 3 routing, user permissions, server network settings, authentication and web server certificates. By default an administrator can access the Admin Web Interface by visiting this address in a web browser: https://Eternal Nasserverip:943/admin (Please paste this url into your browser and replace "Eternal Nasip" with the IP or hostname you allocated to your Eternal N-as instance)

Connect Client: 
The Connect Client Interface is a component of Eternal N Access Server that allows users to connect to the N directly through their web browser. The Connect Client also gives the user options to download their configuration files which can be used on other Eternal N clients.

Eternal N Connect Client
Eternal N Connect Client for Mac
Eternal N Community Client (For Linux/Windows) 

Initial Configuration:
In order to install Eternal N Access Server there are a few things that will need to be looked at;
- Linux Distribution
- CPU Architecture

Note: If you decide to use one of our virtual appliances please refer to one of these guides instead:

VMware Virtual Appliance
Hyper-V Virtual Appliance

Linux Distribution:
You will need to make sure you download the package that corresponds with the current OS Distro, we currently support these Linux Distros:
- Ubuntu
- RHEL
- Fedora
- CentOS
- openSUSE
- Debian

Click here to download the Eternal N Access Server packages

CPU Architecture:

You will need to make sure you install the correct package depending on your CPU Architecture (32bit or 64bit)
Installing the Eternal N-AS Package:

To Install the Eternal N-AS package in Ubuntu or Debian you will need to run this command:dpkg -i Eternal Nasdebpack.debTo install the Eternal N-AS package in CentOS, RHEL, or Fedora you will need to run this command:rpm -i Eternal Nasrpmpack.rpmThe Admin Account for Eternal N-AS needs to be setup through terminal by doing the following:Change the password:passwd Eternal NYou will then be prompted to set a password for the user Eternal N, after setting the password you can login to the Admin UI with the Username Eternal N and the password you set.Note: In some circumstances for certain configurations you may need to run the complete on-init script terminal: /usr/local/Eternal N_as/bin/on-init
Configuring the Admin Web Interface:

After you have completed the Initial Configuration Tool you should then be able to access the Admin Web Interface through your preferred web browser. You should have noticed an link to the Admin Web Interface after you completed the Initial Configuration Tool, if you missed it you can access the Admin Web Interface by typing the following in your browsers address bar: https://Eternal Nasip:943/admin (Please replace "Eternal Nasip" with the IP you allocated to your Eternal N-as instance)
You can now go ahead and login with your Eternal N admin credentials. Once logged in you will see the following screen:

  • 0 أعضاء وجدوا هذه المقالة مفيدة
هل كانت المقالة مفيدة ؟

مقالات مشابهة

Installing App on a Mac OS

Installation Guide For Eternal App Connect Client On MacOS   BACK TO DOCUMENTATION...

Installing App on a Windows Machine

Installation Guide For Eternal App Connect Client On Windows   BACK TO...

Guides For Web Player Version

Deploying The Access Servr Appliance On VMWare ESXi   BACK TO DOCUMENTATION...

Powered by WHMCompleteSolution