Deerfield > Support > VisNetic Firewall > Release Notes

VisNetic Firewall Release Notes

VisNetic Firewall v3.03 (Released October 29, 2007)

Bug Fixes:
* Fix to bug that was preventing manual additions to MAC address groups
* Fix to bug with trusted MAC addresses
* Fix to bug that was preventing the importing of entries to a MAC address group
* Fix to bug that caused "unknown message code" entries to be written to the log file
* Fix to bug in the Port Scan Exceptions code
* Fix to bug that could cause corruption to Groups (IP/Port/MAC) when administering the firewall through the Remote Admin Tool

VisNetic Firewall v3.02 (Released August 23, 2007)

Bug Fixes:

- Fix to bug that could cause the firewall to crash if the user attempted to sort an IP Group

VisNetic Firewall v3.01 (Released August 8, 2007)

Improvements & New Features:
* DNS Names - rules can now be based on DNS names in place of IP addresses. For example, you can now create a rule allowing RDP access _only_ from a particular host machine (i.e. your laptop running a dynamic DNS client, i.e. DNS2Go)
* Added a Port Scan exceptions list. You can now designate IP addresses that are exempt from the Port Scan setting "Ban the IP address of the scanner". This is useful for people who want to ban (unknown) port scanners, but need to allow a monitoring application to scan their system.
* Added a registry value for ICMP stateful inspection timeout.
* Added the ability to modify IP Groups from the command line. Following is the command set that is available:
dfw.exe -ipgroup update -name {name of group} -file {filename} dfw.exe -ipgroup add {address, address1-address2, address/mask} -name {name of group} dfw.exe -ipgroup delete {address, address1-address2, address/mask} -name {name of group}
These commands will allow you to add/delete/modify IP Address Groups. For example, let's say you have a rule that is allowing access to your SQL Server on port 1433. The Remote Addresses that this rule will apply to are in an IP Group that you've created called SQLAllow. If you want to add IP address 209.103.14.89 to this group (meaning that this IP could then connect to the SQL Server), the command line would be: dfw.exe -ipgroup add 209.103.14.89 -name SQLAllow
Command functions: update - will replace the entries in the group with those in the filename you have specified add - will add IP's to the group (can use single addresses, ranges, or address/mask combinations) delete - will remove IP's from the group
* Added an external log viewer application that allows you to create filtered views of your firewall log entries. This application requires Microsoft's .Net 2.0.

Bug Fixes:
* Fix to Ports display not working on all 2003 Servers
* Fix to Remote Admin Tool not displaying IP Groups correctly after making a change to the group.
* Fix to Remote Admin Tool not displaying log entries.
* Fix to default values for NTP client and server rules.
* Fix to certain log entries being displayed twice.


VisNetic Firewall 2.3 January 12, 2006

Minor Improvements:
-New icons have been added for the system tray to display the current state of the firewall. This will help remind the admin if they leave the firewall state to Allow All or Block All.
-Added "One Address" option for all IP address entry fields.
-Numerous updates to the status bar; now shows current state of the firewall, log sort order, state of remote admin connection, updates to the Tarpit and Ban sections.
-New right-click menu option in Ban List window to reset "Attempts Count".
-Update to the Maximum URL length in the HTTP Filters - new possible maximum length is 4095 characters.
-Log view sorting now uses the registry to keep track of sorting directions.
-When viewing the Connections window, status bar will now show the number of Established connections.

Bug Fixes:
-Fix to HTTP Filtering not working correctly for POST data with multipart forms.
-Fix to Remote Admin Tool corrupting the profile for the remote entry if the user logged out before exiting.
-Fix to Remote Admin Tool not displaying log entries.
-Fix to rules being lost when the firewall is not shut down normally.
-Updates to memory allocation routines for the HTTP Filtering driver.
-Fix to problem with rule saving when a password is set.
-Fix to problem with Stateful Inspection when VisNetic Firewall is running behind a PIX firewall.

VisNetic Firewall v2.2.6 December 14, 2004

-Fix to items under the File menu not working on Windows 9x or Windows NT.
-Fix to problem with the Reset Attempts Count for the Ban List. If you had an entry in the Ban List window highlighted and selected Reset Attempts Count from the right-click menu, it was resetting the counts for ALL entries, not just the highlighted entry.

VisNetic Firewall v2.2.5 (as compared to v2.2) November 23, 2004

Minor Improvements:
-Column sorting has been added to the Ban List display.
-Firewall will now remember "last save" path.
-Added confirmation dialog when firewall setting is changed to Block All Entries in the log window can now be changed from descending to ascending by clicking on the Time column header.

Bug Fixes:
-Fix for several bugs that could cause crashing.
-When editing a rule, if it was set to show a port range and you changed it to "one number", the second port field was still displayed.
-When editing a rule, the new Tarpit option was shown only when the Ban option was selected. The Tarpit option is available for Block rules and is not limited to Block+Ban. If you choose just Block+Tarpit, then only connections that match this rule are tarpitted. An offender could be tarpitted on port 21, let's say, but be allowed to connect on port 80. Just for completeness, if the rule were set to Block+Ban+Tarpit and they connect and match this rule, they are banned and tarpitted and any attempt to connect on another port has them tarpitted as well.
-Fix to crash caused by sorting an empty list in the Groups dialog.
-Fix to Groups import not adding new entries to the correct group.
-Fix to Groups import not handling duplicate entries correctly.
-Fix to error on Save As dialog caused by firewall looking for an incorrect path.
-Fix to ban list import not working correctly when importing IP addresses that contain a leading zero in any octet.
-Fix to rules that use Groups not working correctly with the rule was created using the Remote Admin tool.

VisNetic Firewall v2.2 (as compared to v2.1.3) January 16, 2004

New Features:
[1] Tarpits - A "tarpit" is a trap for troublesome outsiders. Your system accepts connections but never replies and ignores disconnect requests. This can leave spammers, worms and port scanners stuck for hours, even days. Now, entries in the Ban List can be set to be tarpits. Also, block rules can become tarpits: - when "Ban" and "Tarpit" are chosen, the rule creates a tarpit for all IPs that try to connect and match this rule. It tarpits all ports for these IPs - when "Tarpit" is chosen but not "Ban", the rule creates a tarpit only for matching connections. It tarpits all IPs for just the selected port range.
[2] IP Groups - one rule can match more than one IP or IP range. In the program menu, under Rules, an entry is added near the bottom called "IP Address Groups". When this item is chosen, a window appears for adding, editing and removing IP Groups. An "IP Group" is a set of IP addresses or address ranges that will be used together by rules.
[3] Port Groups - one rule can match more than one port or port range. This feature is very similar to the "IP Groups" feature, but applies to TCP and UDP ports. You can now define Port Groups (see the Rules menu, near the bottom) and on the Filtering page when editing a rule, there is a new entry at the bottom of the "Ports must match:" list called "Group". Choose that and the list of available port groups will appear.
[4] MAC rules now support "trusted" status. TCP, UDP and ICMP rules can now be restricted to apply to systems that you "trust" (they use MAC addresses that you specify in MAC rules). You can now make a new kind of MAC address rule where the action, if the MAC address matches, is simply to elevate this packet to "trusted" status. Normal protocol filtering (using TCP, UDP and ICMP rules) continues. If a rule matches but is restricted to "trusted" MAC addresses, then the packet will match if and only if it received "trusted" status by a MAC rule. All other packets will not match and the search through the rules will continue for a matching rule. Improved Log Display information
[5] MAC Groups - one rule can now apply to more than one MAC address.
[6] The log display (when you double-click on a log entry) is improved to show the protocol fields and the contents of the packet that triggered the log entry. This display screen also gives you the option to save the packet information you see to a file (in the Log directory, the file name is based on the timestamp).
[7] Block All option on the Configuration Screen - On the Configuration screen (for each adapter), the "Block All" option has been added so you can choose to block all traffic for that adapter (others can "Filter" or "Allow All")
[8] Command-line addition of Ban List entries - To help link other programs (email, IDS) to the firewall for banning IPs, the following command line can be used:
DFW.EXE -ban (address) [-expiry {dwn}] [-tarpit] [-reason "(text)"]
where
(address) is the IP or IP range, in one of the following formats:
#.#.#.# - a single IP address
#.#.#.#-#.#.#.# - an IP address range
#.#.#.#/#.#.#.# - a masked IP address
#.#.#.#/N - a network range (N is typically 8, 16 or 24)
-expiry sets when the entry expires (d=1 day, w=1 week, n=never)
-tarpit sets this ban entry as a tarpit
-reason sets the "Reason" text field (a reminder of the cause of the ban)
The (address) is mandatory, "-expiry", "-tarpit" and "-reason" are optional. If "-expiry" is not supplied, the setting shown on Ban List/Properties is used. The default for "-tarpit" is off. The default for "-reason" is "Added from command line". The ban takes effect immediately.
[9] Command-Line removal of Ban List entries: DFW.EXE -unban (address)

Minor Improvements:
[1] The System Tray popup menu has been changed
[2] The "Settings" item has been replaced by the options "Allow All","Filter" and "Block All", to give immediate control over the firewall state. These controls are exactly the same as with View/Settings/When Running controls.
[3] Added remote admin support for display of the tarpit
[4] You can now right-mouse click on an entry in the tarpit and do "Who is ...?", (but you have to click on the first column to highlight the line).
[5] Improved menu icons
[6] Remote admin support for Groups: IP, Ports, MAC
[7] When a workstation license is found on a server system, the popup message used to simply say, "Bad License". Now it explains that a server license is required on a server windows platform.
[8] The number of entries in the Ban List is now displayed in the Status Bar.
[9] Added a check for block rules that would prevent passive FTP data channels from being allowed. (Version 2.1 introduced support for Passive FTP where a rule was not required, Stateful Inspection automatically recognized and allowed the data connection. Block rules covering the port range used by Passive FTP data connections would conflict, and this warning is to keep this from happening)

Bug Fixes:
[1] Fix for Win2003/IIS 6.0 crashing problem
[2] Fixes a bug in the Ban List where IPs were not getting banned under certain conditions.
[3] Port scan detection was creating false alarms when detecting ACK scans. For now, ACK scan detection is removed.
[4] Block rules were sometimes displayed with the "-->" or "<--" arrows when they should be displayed as "<-">"", since they block connections in both directions. ..Q.

v2.1.3 November 24, 2003
Minor Improvements:
- Support is added for the Ports display in Remote Administration.

Bug Fixes:
- Using the remote admin to add entries to the Ban List corrupted previous entries.
- Fixed bug in HTTP filtering that affected IIS 6.0 on Windows 2003 Server, caused IIS to stop responding until it was stopped and restarted.
- When a rule banned an IP address but the rule did not generate a log entry, the "Reason" put in the Ban List entry showed the device number incorrectly. It was always one less than it should have been.
- The Log2PCAP program could not open the log file while the firewall was running.

v2.1.2 October 7, 2003
Minor Improvements:
- Added a new utility, "Log2Pcap", a tool that converts the packets logged in the firewall's log file to PCAP format for inputting into popular apps such as Ethereal.
- A warning was added if port 443 was added to the HTTP filtering list (since HTTPS traffic on port 443 is encrypted and cannot be filtered)
- The file extension for Ban List files was changed to .TXT
- When the firewall reads a rule set that is an older format, it saves a copy of that file before converting it to v2.1's format.
- Improved the log message written when the user pauses/restarts logging to disk.
- The new toolbar button for Pause/Restart logging to disk (and screen) was moved to the left of the Clear log display button.
- New button is added to the tool bar to Pause/Resume logging to disk.
- New rule option: "Block+Ban". IPs that match this rule will be added to the Ban List. This feature is found on the Actions page of the rule editing page.
- New rule option: "Block outgoing connections". This is for TCP rules so you can make a rule for either outgoing connections or incoming.
- FTP/PASV support. Now, a separate rule is not needed for passive FTP connections (when Stateful Inspection is turned on). Stateful Inspection watches for the passive connection being negotiated and automatically creates a State Table entry in anticipation of this connection.
- New menu options: Import/Export IP addresses to/from the Ban List.
Entries for import can be
1) single IP addresses: #.#.#.#
2) a range of addresses: #.#.#.#-#.#.#.#
3) Address/Mask notation: #.#.#.#/#.#.#.#
4) Address/Class notation: #.#.#.#/C (where C is typically 8, 16 or 24)
- "Reason" column added to the Ban List to explain why an entry is there.
- New Control: SYN Flood Threshold, the packet rate at which a SYN flood is declared. The default is 50, but it can be set to any positive number.
The control for this option is in the menu: SYN Flood/Properties.
- New option: On the log display, a right-mouse click option is added called "Find" to search the displayed log messages.
- The "Activity" window (Server version only) is renamed "Connections".
- Server version only: A new display window is added: "Ports". This is a netstat-like feature which shows active TCP and UDP ports. Not all TCP ports are shown (specifically those that will appear in the "Connections" window, formerly called "Activity"). The application and its path are shown as well, except for system-related connections.
- New Control: Menu option added under View to control Autoscroll of log display.
- When firewall starts, it shows the display that was shown when the firewall last exited (except Configuration and Rules screens).
- New Control: Ban List/Reset Attempts count - this control resets all the counters to 0 (in the Attempts column of the Ban List display). The counter has an upper limit of 255, after which the firewall doesn't report more hits on this ban. By resetting the count, new hits will be reported again.
- Added remote admin support for the File/Renumber Rules control.
- New control: Ban List/Search - search the Ban List to see if an IP address is banned.
- Added new menu control Filtering/Learning Mode, to turn on and off prompts for new HTTP methods and extensions
- For new "Block+Ban" feature in rules, no "Reason" was shown in banned entries if no logging options were set. A simple reason is added, showing the device number and rule number that resulted in the ban.

Bug Fixes:
- New SYN Flood menu item was not greyed out when using password protection
- When using password protection, the firewall would prompt for password entry on startup under certain circumstances.
- Ban List/Reset Attempts count option was not greyed out when the Ban List was not displayed.
- When editing a Ban List entry, the Reason field could not be scrolled.
- The Ban List/Import feature wasn't reading all entries of the file
- (Server version) The Remote Admin menu item was moved to the left of the View menu item.
- Updated Configuration Wizard to use port 5190 for ICQ.
- When editing rules, if you hit the ESC key when editing the Description field (on the first page), the page went blank.
- With remote administration, when editing a firewall entry, if the name was changed, the name in the display was not updated until the app was stopped and restarted.
- The newly-added feature of starting on the same display as you left when the firewall was stopped cause the password prompt to come up when the firewall was started (when using password protection).
- A ban list with overlapping entries could result in IPs being allowed when they should have been blocked.
- Autoscroll for the log display was disrupting other displays.
- Fixed bug in Learning Mode that could crash the system.
- On the Settings/When Running page, setting the Learning mode toggle did not activate the "Apply" button.
- Fixed a bug that could cause a crash when using FTP/PASV mode.
- Workaround for apparent bug in Windows NT4 dialup device driver. Symptoms were that small packets, such as ICMP and UDP would pass but larger packets (e.g. TCP) were blocked.
- When the remote admin tool was run on the firewall system, it was turning off HTTP filtering when it exited.
- When rules were enabled/disabled, the display was jumping to the top of the rules list. (NOTE: This is still happening when rules are edited. This will be addressed in the next release)
- HTTP filtering menu items and toolbar button are grayed out if the feature has been disabled or password control has restricted access to them.
- On NT4, the HTTP filtering was not being disabled properly. The result that NetBIOS was not working (filesharing, network logon).
- The new ban checkbox on the rule editing "Actions" page was not being displayed properly under certain circumstances.
v2.0.7 August 6, 2003
Minor Improvements:
1) Compatibility with AtGuard on Win9x. With previous versions, the Win9x system would crash when AtGuard started.
2) The feature Filtering/Trusted IP Addresses had a confusing title, since entries in this list were simply exempt from HTTP filtering. The menu item and list title have been changed.
3) In the Settings window, the last page you viewed is "remembered" when you reopen it. That is, the next time you open Settings, you start at the page you were on when you last view it.
4) Added support for Windows Server 2003.
5) In remote Administration, when you connect to a remote firewall, the computer screen turns blue, not red. This is because red is considered an indicator of trouble.
6) When the firewall starts, Stateful Inspection does not kill active connections (TCP connections that send/receive within the first few seconds of when the firewall starts). Only connections allowed by the ruleset are allowed. This solves a problem for Terminal Services users who want to open a T.S. session and start the firewall from within it. Previously, doing this would then cause the T.S session to be blocked, because it wasn't recognized by the Stateful Inspection engine.
7) License upgrade period now enforced. Prior versions ran for all valid license. This version works for licenses that include upgrades up to at least July 1, 2003.

Bug Fixes:
1) One type of port scan resulted in an error in reporting - the source IP address (the one scanning you) appeared as the destination address as well, instead of your address.
2) Activity display would disappear within seconds on remote admin connections.
3) On the rule editing "Actions" window, the controls were out of order when tabbing through.
4) On the Rules display, the app wasn't properly keeping track of when a line was selected and when it wasn't.
5) When the user logged off and then back in, the display would flicker.
6) For remote admin connections, the Log/Copy menu options did not work.
7) Remote connections would break if the administrator switched repeatedly between windows for an extended period of time (20 seconds).
8) View/Log menu options were not grayed out properly.
9) When using the Remote Admin tool and right-mouse clicking in the Control window, the "Settings" menu item was being displayed when it shouldn't be (it applies only to the firewall).
10) A bug introduced in v2.0 stopped the message from being written to the logfile when the firewall stopped due system shutdown.
11) In the Remote Admin tool, the help file was not accessible.
12) Expired entries remained in the Ban List if it was displayed at midnight, when old entries are cleared.
13) The Remote Admin menu item was appearing in a different order on Win9x compared to NT4/2K/XP.
14) Under some circumstances (Terminal Services), the position of the window was getting lost, making it only viewable if it was maximized.
15) The Ban List was showing duplicate entries if the firewall ran for more than two days. This happens when entries expire.
16) On NT4, the Filtering/Enable menu option caused the AMBRAPP.SYS driver to load incorrectly, causing a crash on reboot.
17) Fixed bug where changes to the default settings under the Advanced button (on the Configuration screen) using remote admin were not saved.
18) In remote admin, when going from the Rules screen to the Ban List, the entries were shown twice.
v2.0.2 July 10, 2003

Minor Improvements:
1) HTTP "Connect" method added to the Denied List.

Bug Fixes:
1) Newer menu items were not disabled when Password Protection was being used.
2) Fixed bug introduced in v2.0 RC2, configuration was not saved at shutdown.
3) On Win9x, the Ban List/Properties dialog box didn't come up properly.
4) Fixed a bug in HTTP filtering where reporting certain traffic caused a crash.

v2.0 (June 2003)

New Features:

Remote Administration - Servers Only
Access individual VisNetic Firewall installations or entire Firewall networks from remote locations. This feature provides incomparable freedom, and complete control over a network using password protection. Administrators can access every setting in Firewall installations without having to access each computer.

Web Server Protection - Servers Only
VisNetic Firewall 2.0 scans open ports to your web server and blocks malicious attacks upon detection. Web Server Security Features include: Specify Acceptable Methods/Commands - Disallow malicious commands that request unwanted activity, and accept valid requests. Filter Character Sequences - Reject suspicious character sequences that are often used by hackers. Provides an additional layer of security through analyzing URL characters that are telltale signs of hack attempts. Block URL File Name Extensions - Determine inappropriate file name extensions (.exe, etc.), and prevent users from running programs on your web server (such as NIMDA).

Port Scan Detection
Detects all TCP port scans, including: connection scan, NULL, ACK, Window, FIN, Xmas and Full-Xmas. Port scans are frequently used before hack attempts. Controls are available to modify the scan to your environment and to ban port scanners automatically.

Ban IP Addresses
Allows administrators to ban individual or groups of IP?s, and provides the necessary utilities to customize the ban list to meet requirements. Bans can be set permanently, or to expire after 1 day or 1 week.

Filter by MAC Address
The ability to allow or deny a computer by its MAC address ensures that malicious or unwanted users are unable to bypass security filters.

Minor Improvements:

- Added buttons to the HTTP filtering "Methods" page so you can add and remove methods (as on the Extensions page).

- Terminal Services options (both client and server) are added to the Services list (on the Filtering page, when you create/edit a rule) and to the app list in the Setup Wizard.

- The Setup Wizard asks if Remote Administration will be used. If yes,the user enters the password (and port number - 8519 by default).

- Replaced Filtering menu options "Turn filtering off" and "Turn filtering on" with "Disable" and "Enable". These actually set whether the filtering driver is loaded, so users without a web server do not have to have this (no performance impact).

- Added menu option View/Status Bar to toggle the display of the status bar.

- Log display has autoscroll - go down to the bottom of the list and it will stay there.

- Additions to the help file.

- Setup Wizard has new "Allow" option for remote installation - if you chose to make your ruleset later, you are prompted whether you want the firewall to allow all traffic when it runs or block.

Bug Fixes:

- Fixes handling of very small TCP, UDP and ICMP fragmented packets(they were being blocked incorrectly)

- Port scan detection was not being done on Windows 9x (NT4, 2000, XP were OK)

- Fixed display bug where rules were not refreshed sometimes after editing a rule.

- Fixed initialization of HTTP filtering for systems with a web server.

- Choosing the menu item Port Scan/Properties was minimizing the main window.

- Fixed right-mouse click "who is" option for new port scan log message.

- On some systems, the firewall app could be started more than once (not allowed) because the second instance couldn't find the running instance. Now, if you try to run it a second time, it will pop up the program window.

- Error checking on the window position and size. One symptom of the problem is that you can see the program UI maximized but cannot "Restore" to normal size.

- When the Ban List had exactly one entry, the check for expired entries was not working.

- Removed "Ethernet" from the "Common Protocols" list under Configuration/Advanced.

- Fixed incompatibility with XP's QoS service, which caused incoming connections to be blocked when Stateful Inspection was in use (more specifically, when the Sequence Number Hardening feature was in use).


v1.2.1 (Jan. 2003) (Last update before v2.0)

Minor Improvements (v1.2.1):
  1. Fixed incompatibilities with WinGate.
  2. Added feature to allow renumbering of rules
  3. Added feature to write the configuration in readable form.
  4. Reminds user if license is expiring soon, so they aren't caught by surprise when it does.
  5. Improved ICMP rules in default rulesets.
  6. Fixed display bugs in IP Tracer program.

Bug Fixes (v1.2.1):
  1. Fixed handling of PPPoE.
  2. Fixed Win ME bug where connections could sometimes hang.
  3. Fixed Stateful Inspection of ICMP
  4. Fixed bug in rule import.
  5. Fixed bug in log send plugin, where it was crashing occasionally.


VisNetic Firewall v1.2 - Sept. 4, 2002

CHANGES AND NEW FEATURES

  • Changed menu text:
    File/New Ruleset...
    File/Load Ruleset...
    File/Save Ruleset...
    File/Save Ruleset as...

  • Added SYN Flood Protection

  • Added new driver for XP to fix problem with "Network Neighborhood" ("My Network Places")

  • Added controls for changing the Stateful Inspection timeout for TCP

  • Added a warning message for File/New Ruleset to point out that all traffic will be blocked after this command until new rules are added

  • On shutdown, it won't prompt for password (if password security in use)

  • Added menu item Help/DSL setup to help DSL users with PPPoE

  • Fixed bug affecting some XP drivers where packets were not received properly

  • Fixed bug in Plugin DLLs where closing '>' was missing in email address strings

VisNetic Firewall v1.1 - June 11, 2002

CHANGES AND NEW FEATURES

  1. New NT4 firewall driver supports dialup and rids the user of added steps to install and uninstall.
  2. Added combo boxes to help set port values in Rule/Filtering page.
  3. Added "Allow All" and "Block All" buttons to Server version's "Other IP" page. (Adapter/Configuration/Advanced)
  4. Fixed a bug in the adapter IP display to handle large numbers of IPs on one adapter.
  5. Fixed a bug in the rule 'Delete Code' that could cause the program to crash.
  6. Changed the rule 'Display' to say "All Ports" if range is 0-65535.
  7. If VisNetic Firewall is run a second time, the program window is brought to the foreground before the second instance exits. (Previously, the second instance just stopped silently.)
  8. When run as an NT service, VisNetic Firewall does not prompt, "Are you sure?" on the exit. (Makes it easier for Advanced Servers and Terminal Servers.)
  9. Wizard-made TCP rules have the "Log Connections" flag set to provide valuable feedback.
  10. Fixed the bug that mixed the UI colors whenever a user changed them to the default Windows background color.
  11. Setup Wizard - mail server rules - fixed to add rule for outgoing SMTP.
  12. Allows a rule to be deleted with the "Delete" keyboard key.
  13. Allows selecting of multiple rules for deletion.
  14. Allows selecting of a block of rules to move up or down.
  15. Rule number is put in title of rule editing window.
  16. RealTek and SMC drivers on WIN2000 fixed.


VisNetic Firewall v1.0.3 - April 2, 2002

CHANGES AND NEW FEATURES

  1. Corrected typo in popup message for Win2K users with NetBEUI installed.
  2. Fixed bug in display of IP addresses to handle a large number of IPs assigned to one adapter.
  3. Improved display of rule description when it is on multiple lines.
  4. Fixed bug in settings for "Other IP protocols" under Configuration/Advanced, where in some cases, the controls did not change the setting.


VisNetic Firewall v1.0.2 - March 12, 2002

CHANGES AND NEW FEATURES

Firewall engine:
  1. Added rule number to title of rule editing dialog.
  2. Fixed bug that caused hang in Log/Closest Rule?
  3. All help buttons work.
  4. Added <Ctrl-C> for Log/Copy and <Delete> for Rule/Delete.
  5. Added selection of multiple rules for deletion.
  6. Fixed issue on Win2K where NetBEUI had trouble binding to NDISWAN devices (e.g. dial-up).
  7. Fixed default screen size to show all on Configuration screen.
  8. Allowed moving multiple rules up/down.
  9. Fixed display when background color changed.
  10. Added Log/Copy/Source Address or Destination Address.
  11. Fixed so that selected log item remains visible when new lines added.
Configuration Wizard:
  1. Added registry find for NetOp Guest and Host.
  2. Added SMTP rule for email servers so they can send to each other.
  3. When user says system is not a gateway, ephemeral port ranges are 1024-5000, not 1024-65535.
  4. SetupWizard checks ruleset file names to make sure they exist.

VisNetic Firewall v1.0.1 - February 13, 2002

CHANGES AND NEW FEATURES

Name changed from Ambra Firewall to VisNetic Firewall

Ambra Firewall v1.0.0 - January 22, 2002

Select a Product:

Online Support
Site Search:

Advanced