Table of Contents
The options menu can be accessed to modify the NOVAXE® administration and report rendering parameters. It has two submenus which are:
Configurator: allows you to change the webserver configuration.
Report template: allows you to change report rendering parameters.
they are both accessible from the left column menu.
The following options are available:
Bind address: this is the TCP/IP address on which the webserver-configurator is listening to incoming connections. The drop list menu shows all the available addresses that the server can bind. By setting the 127.0.0.1, the configurator will listen only on connections coming from the local machine. By setting a 0.0.0.0, the configurator will listen on all available IP addresses (including the local host).
Bind port: the TCP port on which the webserver-configurator is listening to. By default it's port 8081. It is recommended that you leave the default port unless some other application on your host uses it.
Allowed IPs: This is a comma separated list of machine IP addresses which are allowed to connect to the webserver-configurator. Use * if all machines can connect.
Notice that the above list means only that if an IP is allowed to connect, if it does, the configurator won't refuse the connection. However whether a particular host can actually reach the machine where NOVAXE® is installed is outside the realm of the configurator. For example if a firewall is blocking access to your host or no routing is available, the remote client will be unable to connect, no matter what NOVAXE® configuration is.
Password: this is the password to be used to access the configurator. Please, remember that the username to use for loggin in is: admin.
Confirm password: you must retype the password here to ensure that you didn't mispelled it the first time. If passwords do not match, you won't be able to update the configuration.
Click on confirm and then confirm again to update the configuration. Notice that the configurator needs to restart. Please, ensure the parameters suplied are correct because you can loose access to the configuration if for example you're connecting remotely and you switch the configurator to bind only the 127.0.0.1 (localhost) address. Once restartet you won't be able to log-in remotely because it won't be listening on the external interface anymore. Same risk if you deny yourself access by wrongfully altering the Allowed IPs: entry list.
NOVAXE® stores this configuration in the params.cfg file, placed in the config subfolder of it's installation root.
Passwords in the params.cfg file are base64 encoded and may not be directly accessible or editable. Still if you forget the log-in password you may actually reset the content of the adminpwd field to empty string in order to restore the default password (which is: password). Just remember to manually restart the "NOVAXE® configurator" from the Windows Services applet.
The following options are available:
Memory model: The memory model used (small, medium or large) affects reports details. In particular, collecting statistics for each host seen by the firewall takes up RAM memory. While an internal network has typically a relative small number of hosts and poses no problem, the external network if it's the internet may generate a high amount of events with host accessing (or tring to access) your local resources (such as DNS, FTP, HTTP servers, etc.), resulting in a huge amount of memory used by the reporter to keep track of all these events. Depennding on what you want in your report, how much large is the timerange of your report and how much memory your host has, you may be willing to alter this parameter to taylor the reports to your needs. In general however, if you do not need the external hosts activity, use a small memory model, which is of course the most conservative, for it's easy to quickly run out of memory. With the small memory model however the External ports to monitor parameter of the Device menu is ignored and no traffic per external source host per port is present in the report generated.
CPU usage: this parameter tells the reporting engine how much CPU to use while creating your report (that is, reading log files and rendering the PDF). You may set it to high only if you are sure no other critical applications are running on your host or you have a multiprocessor system that can easily sustain the load. Otherwise your system may become partially or totally unresponsive and very slow at other tasks while creating reports.