nForce UDA Package
If you're already familiar with firewalls and the TCP/IP stack, then you may want to just the "Advance Configuration". You will have dozens of settings that you can modify. You may choose to allow or block specific TCP options or even specific your own TCP "Rule".
As with the Ethernet statistics display, you may also display the statistics of your firewall. The graphically display will show you the total number of Packets Or Connections, blocked or allowed.
The NAM keeps very detailed logs of attacks, changed settings, and other things. While it does not display the information in real-time, you can manually "update" it by clicking the "refresh now" button. You may even "Export" the logs to a text file for further annalist. I would have like to of had the option to export the logs to a excel spreadsheet or other file formats. One problem I found with the firewall logs, is that there is no option to only see a list of events from a specific IP address. This is useful when someone is attacking your machine, and you want to grab all of the attack information that originated from their IP address, to email their ISP about abuse.
For example, if you had a user attacking you it's going to be a hard task to swift through all of the logs to only find that specific attacking IP address.
Maybe these features can come in a later updated version.
We just had to test out the firewall to see how well it could hold up to a very hard attack from the outside. We also wanted to see how much CPU usage the firewall was going to use, while launching this attack. We sent 10,000 packets of data every second to TCP port 80. Clearly, this put a HUGE load on the firewall as the CPU usage hung around 75% most of the time. The GigE NIC operates off of the PCI bus, much like traditional intergraded NIC's and this makes the CPU load high under an attack or under intensive file transfering. The new nForce 3 250GB operates differently because it bypasses the PCI bus all together to provide much better performance and much less CPU load. However, we won't get in to that today :)