FreeNAC is quite complex, and needs a machine with GNU/Linux and many OpenSource source tools installed.
To get you started quickly with FreeNAC, we have built a Virtual Appliance (also called a Virtual Machine, VM) with Linux, the modules needed, and FreeNAC installed in a 'demo mode'.
The VM is ideal if you just want to test FreeNAC, or feel daunted by the length installation documentation for FreeNAC.
On the other hand, the VM is only updated every few months, and its slow to download.
There are two datasets included with the VM: "nacdemo" contains an example that should help to understand the GUI and what information FreeNAC stores, whereas "opennac" is an empty dataset ready for productive use.
The FreeNAC version included in the VM is the latest stable branch at the time the VM was created, from the Subversion repository.
The VM will try to get an IP address via DHCP, which you can see with
Optional changes to the VM:
The Windows GUI is the primary, recommended, method of administering FreeNAC .
Please follow the instructios in the section Installing the Windows Interface.
See the Users Guide for a description of how to use the Windows interface.
Point your switch(es) to the FreeNAC VM (see the technical Guide (http://freenac.net/en/techguide).
You may also need to define your SNMP RO/RW communities in your switches. Some scripts (namely cron_restart_port.php) require to know these communities in order to operate properly. Once you've defined your SNMP communities on your switches, edit as root the file /opt/nac/etc/config.inc, find the lines:
## SNMP communities
$snmp_ro="PASSWORD2"; # maybe public
$snmp_rw="PASSWORD3"; # very private
$router_ro="PASSWORD4"; #For router_mac_ip script. If empty, use snmp_ro defined above
and change PASSWORD2, PASSWORD3 and PASSWORD4 accordingly.
Once you've done that, check for the existence of the file /opt/nac/bin/cron_restart_port.pid and if it exists, delete it
Observe syslog and play with the GUIs.