RipEX2 can be easily managed from your computer using a web browser. If there is an IP connection between the computer and the respective RipEX2, you can simply enter the IP address of any RipEX2 in the network directly in the browser address line and log in. However, it is not recommended to manage an over-the-air connected RipEX2 in this way, because high amounts of data would have to be transferred over the Radio channel, resulting in quite long response times.
When you need to manage an over-the-air connected RipEX2, log-in to a RipEX2, which your computer is connected to using either a cable (via LAN) or a high-speed WAN (e.g. Internet). The RipEX2 which you are logged-in to in this way is called Local. Then you can manage any remote RipEX2 in the network over-the-air in a throughput-saving way: all the static data (e.g. Web page graphic objects) is downloaded from the Local RipEX2 and only information specific to the remote unit is transferred over the Radio channel. RipEX2 connected in such a way is called Remote.
When in Router mode, the IP address of either the Radio or Ethernet interface in the remote unit can be used for such a Remote management. IP routing between the source (Local RipEX2) and the destination IP (Remote RipEX2) needs to be configured properly.
When in Bridge mode, IP address of the Network interface the Radio interface is bridged with is used for Remote access. When accessing the unit locally the IP address belonging to an Ethernet port, the management PC is connected to, is used. Be careful, each RipEX2 MUST have its unique IP address and all these IP addresses have to be within the same IP network (defined by the IP Mask) when Remote management is required in Bridge mode.
For the sake of security only HTTPS protocol is used for the connection between the web browser and RipEX2 unit. If the http://… is used into the web browser address line, the communication is immediately automatically redirected to https protocol.
For better protection against unauthorized access to the network there is a timer build within the RipEX unit and the web interface (set to 24 hours by default), which is monitoring user activity. In case of user inactivity, the connection between the web interface and the unit will be interrupted (i.e automatic logout). Timer is automatically launched in parraller both in the unit and in the web browser. In case of changing the timer setting, we recommend to relog (logout, login), so the correct initialization of timeout inactivity can occur.
The login page informs you about the Unit name and IP address of the RipEX2 unit you are trying to log in.
The login page allows changing of the language of the whole web interface (English language is default).
Web interface is designed for usage on all kinds of equipment – with different screen sizes and screen resolutions. Most of the pictures depicted in this User manual are taken on the desktop type of screen resolution.
Web page header
The header of each web page contains:
Unit name and
IP address of the RipEX2 unit you are connected to
Identification of the web current page (2nd or 3rd level of the menu)
Remote access button
Changes to commit button
Refresh settings button
User menu button
Supported web browsers for desktop are current versions of:
Supported Web browsers for mobile equipment are current versions of:
Safari for iOS
Chrome for android
All changes of configuration parameters are marked by different color.
Multiple configuration changes in various menus can be prepared prior to final Commit.
Changes to commit “basket” collects all the changes.
Apply (Save to radio unit) all the changes using Send Changes or
Discard all changes via Reset All
With RipEX2 new way of showing important system events to the user is introduced. It is called Notification Centre and is used consistently throughout the interface. Notification Centre is located on the top right corner of the interface. It exists in two forms: active notification display and full Notification Center. Both the active notification display and the full Notification Centre are displayed either below the top header of the interface or in the right hand sidebar depending on the size of user’s display. The behaviour is responsive so in case the user needs to make the browser window narrower the notification center automatically changes place to use the most efficient location.
Notifications are mostly triggered by user actions in the interface, for example success or failure of Fast Remote Access connection. They are not to be confused with Events, which are triggered mosty by the system and are not shown in the Notification Centre, but on Diagnostics > Events page. In other words Notifications are caused by the user, Events are caused by changing status of the unit.
Every new notification is displayed in the Notification Center drawer. User can either dismiss the notification by clicking the cross in the notification body, close all displayed notifications in the drawer or expand full notification centre using buttons (“Close all” and “Show all”) on the right side of the notification centre drawer.
Notification Centre collects all notifications that have not been dismissed and allows users to browse them.
This functionality is available on individual web pages of the graphical user interface by clicking of the purple box with the question mark on the right upper corner (or in the middle) of the screen (according to the width of the screen).
The content of the help is identical with the respective sub-chapter of the User manual.
RipEX2 unit management is designed to work smoothly even when the unit under configuration is connected via relatively slow radio channel. In case of locally connected unit – direct configuration of the unit (accessing the unit IP address directly from the web browser) works fine. If the unit should be connected remotely via the radio network, the so-called “Remote access” needs to be used to configure and manage remote unit using bandwidth friendly volumes of transmitted data. Open the web browser, enter the IP address of a locally connected unit and connect to a remote radio (which needs to be accessible from the locally connected unit via the RipEX2 network).
RipEX2 local unit must have the highest firmware version in the whole network to ensure proper Remote access functionality. Nevertheless it is recommended to keep the same version of firmware in the whole network. See details in chapter Section 7.6.6, “Firmware”
Remote access can be activated via click on the Remote access button.
The connection to remote radio proceeds…
The IP address of the actually connected RipEX2 unit is displayed as part of the Remote access button. All the configuration settings are remotely available using standard web interface. Some of the Diagnostic features are available via local connection only.