- Downloading the ISO
- Burning the ISO Image
- Installing the ISO
- Basic Configuration
- Advanced Configuration
- Registering the redBorder Client Proxy in redBorder Live
- Add a Flow sensor
RedBorder client proxy is a software that has minimum requirements in order to function correctly. The minimum essential elements required for installation (as well as those recommended for correct performance) are shown in the following table:
|RAM||1 GB||2 GB|
|Processor||1 Core||2 Core|
||16 GB||32 GB|
Downloading the ISO
In order to download the ISO image, you must be registered. In this user guide, the entire registration process and first contact is explained.
Once you are logged in to the redborder web, you must go to Community -> Downloads. On this page you will find all of the redborder editions along with their corresponding specifications and characteristics.
To download the redborder client Proxy, click here:
* RedBorder Live only compatible with versions higher than 18.104.22.168
Burning the ISO Image
The ISO image is prepared to perform the boot from a DVD reader, USB device or as an ISO file for a virtual machine.
In order to burn the ISO image from a Linux system to a USB device, the following command needs to be used if the USB device is mapped in /dev/sdd:
[root@machine ~]# dd if=redBorder-3.1.80-5-x86_64-6.5-proxy.iso of=/dev/sdd bs=10M
Installing the ISO
Once you have booted the redborder ISO, you will see the installation menu. To perform the installation, select the option: Install Client Proxy:
Once in the installation process, you only need to confirm the installation destination and root password. Redborder is prepared for unattended installations, so you should be especially careful with the time you have to respond to these three questions if you wish to modify the default options:
Once this page has been confirmed, the installation will carry out all of the necessary processes to prepare the system for configuration.
By default, the root password will be redborder.
Upon completing the installation process, you can enter the system with the root user and password (redborder by default):
You must note various important parameters on this screen depending on the scenario where the client proxy is going to be placed.
- UUID: is the universally unique identifier that identifies the client proxy machine. You will need it in order to register in redborder Live.
- IP Address: client proxy IP address
- Collector Addresses: Listening ports where the client proxy is going to be collecting the different types of flow (1 port for each type of flow).
- IP Address: client proxy IP address
- Netmask: client proxy Netmask
- Gateway: client proxy Gateway
- Nameserver: client proxy DNS
Registering the redBorder client proxy in redBorder Live
In order to register the sensor in redBorder Live, you must have a redborder account.
In order to register in redBorder Live, you must access here. Click on Create a new redBorder live account.
Fill out the form and click on Register. You will need to confirm the email in order to finish the process.
Now, you must go the RedBorder Live login page. You will log in with the same email address and password that you used in the registration.
Therefore, you must go to LIVE:
Go to Sensors and press +Add Sensor and +Claim Sensor:
A pop-up window will appear where you must enter a name for the sensor and paste the UUID that you copied before in the field below.
Click on save and wait between 5-10 minutes until the sensor is configured correctly.
You must wait a few minutes to get a green indicator.
You can then verify that the sensor is working in RedBorder Live.
Sensor registered and claimed.
Add a Flow sensor
To add a flow sensor must click on the Edit button -> Add sensor -> Flow:
A pop-up window then appears which ask you for a name and the IP address from which the flow of data is being received:
By going to the upper FLOW tab, you can verify that the traffic that was initially receiving the Client Proxy is now classified as Sensor Flow. Once you have created the different flow sensors, the traffic can be viewed separately:
In the case that no information appears in the graph:
- Verify that the client proxy has been installed correctly.
- Check that traffic arrives at the machine.
- If there is a problem with the client's configuration.
- If traffic arrives at the machine but nothing is seen in the web dashboard, contact with firstname.lastname@example.org