...
In secure-processor.properties.j2 template file, the WiFiMon Administrator may select whether to use or not a JSON exporter. This exports measurements of hardware probes towards a JSON collector. It is designed for the eduroam JSON collector, but it could be adapted to the needs of the WiFiMon user. If you want to disable this process, property "json.collect" should be set to "false", otherwise to "true". The URL of the JSON collector should be specified at the property "json.collector".
WiFiMon provides methods for checking if a new software version is available. Therefore, the running version of the WiFiMon software is compared with the most recent version that is stored within a VM provided by GEANT. Moreover, this VM keeps some statistics of WiFiMon end users involving their IP address and running version. The purpose of this is to track how many users are currently utilizing WiFiMon and what software versions. If the WiFiMon end user wants to be excluded from this process, "user.tracking" should be changed to "no" in ui.properties.j2 template file.
...
Note: This step is only required if the WiFiMon Code code is modified by the reader user to include new features.
The WiFiMon code can be obtained from the official repository (https://bitbucket.software.geant.org/projects/WFMON/repos/agent/browse). A requirement to compile WiFiMon code is Apache Maven. It can be installed via the following commands:
...
Within the WiFiMon code folder (cd agent), the WiFiMon code ban can be compiled using the following commands:
...
| Code Block |
|---|
cp agent/wifimon-assembly/target/wifimon-agent-bin/secure-processor-1.4.0.war /usr/lib/wifimon/secure-processor-1.4.0.war cp agent/wifimon-assembly/target/wifimon-agent-bin/ui-1.4.0.war /usr/lib/wifimon/ui-1.4.0.war |
Finally, WiFiMon can be started by using the start.sh script within /usr/lib/wifimon:
Anchor links links
3. The WiFiMon GUI
| links | |
| links |
...