ESTIMACIÓN DEL DESPLAZAMIENTO MÁXIMO DEL BUQUE

Using the Batch Details report it is possible to get valuable information such as the Active Users listing as well as perform actions related to this batch session

A Batch Details report is per a batch session so the text box is an auto-completing input field for all the batch sessions previously created.

Some of the actions available to perform on this report is to generate an invoice and download it which is basically the same output in a PDF file format as the Batch Details report, including the Hotspot information which the batch session is associated with as well as your own company's contact details.

The generated invoice/report can be further customized [1] to include the correct company information, color schemes, logo and other general text you may wish to include.

Emailing the generated invoice is possible with the click of a button and requires that the target email address is defined in the contact information for the hotspot and that the various CONFIG_MAIL directives are properly set in the configuration file.

Image: Reports – Batch Users – Batch Details

The page supports exporting all users associated with the specified batch session as CSV file, as well as exporting only the active users details.

daloRADIUS User Guide Page 107/243

The following image shows how the invoice looks like, which ofcourse can be further customized with the business's own logo, contact details, colors, etc – See the Appendix for this

Image: Reports – Batch Users – Batch Invoice Look and Feel

Dashboard

The dashboard is all about tracking the status of your routers whether they're just access points or act as NAS, but it implements it in a different way than usual.

It is a common practice in the world of monitoring and control systems for a central server to query the network services/servers by standards like SNMP or implementing agents on the client's end though this is not the case with the implementation of the dashboard in daloRADIUS.

The dashboard implementation, which was adopted heavily from the mesh community, takes a different approach – daloRADIUS exposes a web page to which all the routers can connect and send data like their uptime, total connected users and much more. It requires to first install this heartbeat script on the routers and once that's done the script can report every specified interval to the daloRADIUS system.

Moreover, this gives better control since this can act as a two-way communication pipe and turn the process from reporting to actual provisioning by implementing the necessary logic inside daloRADIUS which will return data or commands for the router to act upon.

Another great value of this method of implementation is that it isn't necessary to configure VPN clouds between daloRADIUS and the routers or configure any firewall rules because it isn't required to specifically locate and query each router but rather the opposite – each router can connect to the daloRADIUS server, sitting somewhere on your network or on the Internet, just as if the routers would connect to any other server on the Internet.

daloRADIUS User Guide Page 109/243

The diagram shows the flow process where-as the scripts on either NAS simply perform an HTTP GET request (naturally, over port 80), bypassing possible firewalls on the way, reaching daloRADIUS application which process the request and replies back information if necessary (replying is optional).

Image: Reports – Dashboard – Explaining how NAS heartbeat scripts communicate with the NAS

It is important to remember that the NASes require access to the heartbeat.php file in

daloRADIUS's root directory only and if any extra security measures were taken such as firewalls or user/pass authentication to access the daloRADIUS application then they should be disabled only for that heartbeat script. This is explained in the Configuration -> .htaccess section which discusses granting access to the script via IP ranges and the .htaccess file.

About implementing the dashboard heartbeat script son the NAS routers consult the Appendix

The Dashboard interface composes of the most valuable information in a list view, These are:

• The firmware on the router

• The WAN and LAN interface information: IP and MAC address

• The WiFi interface information such as the configured SSID and possible WEP/WPA Keys

• Various router variable data such as Uptime, memory consumption and bandwidth utilized

Image: Reports – Dashboard – Dashboard Information

The last column, Last Checked-in , provides the most important information – the last time when this NAS reported in. As seen, there are several thresholds which are distinguished by their colors to easily locate NAS not reporting due to malfunction or some other reason.

The thresholds are configurable in the global daloradius.conf.php file:

• CONFIG_DASHBOARD_DALO_DELAYSOFT – The soft delay threshold, by default set to 5 minutes.

If the NAS didn't report within the soft delay time-frame the column is colored in yellow.

• CONFIG_DASHBOARD_DALO_DELAYHARD – The hard delay threshold, by default set to 15 minutes.

If the NAS didn't report within the hard delay time-frame the column is colored in red.

The configuration file also defines a few more configuration directives which are essential:

• CONFIG_DASHBOARD_DALO_SECRETKEY – This is the secret key which is required to be the same through-out all the heartbeat scripts on the NAS routers as well as on daloRADIUS ofcourse, in order to validate that the request is a validated heartbeat script.

• CONFIG_DASHBOARD_DALO_DEBUG – whether to enable debugging, if it's turned on (i.e: set to 1) then daloRADIUS will reply back debug information such as the data it received from the heartbeat script and can be easily tweaked inside the heartbeat.php script itself to return anything else.

1 2 3 4

daloRADIUS User Guide Page 111/243 Accounting

Accounting records provide a facility to track user's service usage based on their connection sessions.

Accounting records are dependent on the RADIUS server configuration to support and enable logging of accounting information to the database as well as the NAS to first and fore-most send accounting information for users.