changelog

An easy, yet highly-configurable iptables-based firewall solution designed for everybody from home u

                      Linux Network Solution Kit CHANGELOG
--------------------------------------------------------------------------------

[0.1.0]
 * Only a slight change was made to detect if the a module exists.

[20020818-0]
 * Corrected detection of absolute path for the config file.

 * Changed default locations of config file and modules directory to "real"
   system directories.  Added a simple install.sh script to do it for you.

 * Added an install function to install modules to the correct directory.

[20020810-0]
 * The code was almost completely overhauled - there's really just too much to
   specify exactly what all was done.  All of the changes should not make much
   of a difference as to what iptables commands are run, but rather HOW they are
   determined.

 * This version marks the first in the next generation of LNSK.  I switched over
   to having one controlling script (lnsk) that runs all of the modules that are
   in the modules directory.  New modules must be named lnsk.<modulename> and
   placed in the modules directory.  The start(), stop(), and restart()
   functions are required of all modules - they are run when "lnsk
   {start|stop|restart}" is run.  When programming new modules, you should not
   have to worry about function interference" (same function names in different
   modules) because each module is run in it's own subshell.

 * When invoking lnsk, you can run a single function of any desired module.
   Simply run "lnsk <modulename> <function> [params]" where <modulename> is the
   name of the module without the "lnsk.".  This can be used for dynamically
   adding rules to the firewall, etc. without restarting the whole firewall.

 * Added the ability to specify a config file via the command line when invoking
   lnsk - "lnsk -c <config_file> <whattodo>".  Note that this must be the first
   parameter.

 * You can now use commas in multiple port declarations even if you don't have
   the multiport or mport match.  You still can't combine colons and commas
   unless you have the mport match.  This should be fixed soon.

 * It's just getting more modular as a whole.  From now on, this changelog will
   be split up between the base module and the firewall4 module.

[20020802-0]
 * I completely changed how I will be releasing files throughout development.
   From now on until I feel like LNSK as a whole is up to at least beta status,
   I will be releasing individual segments of it.  This release, I changed lnsk
   to lnsk.firewall4 since it contains only IPv4 firewall capability.  Even once
   all the files are complete, I will most likely leave them seperate and use a
   wrapper script (probably named lnsk...duh) to control all of the modules.  I
   plan on having only one config file - lnsk.conf - so if you are upgading in
   the future, make sure not to overwrite your current lnsk.conf when extracting
   the new files!

 * All IPv6 functionality (oh wait...what functionality ;)) has been taken out
   of this release.  It will be included in a seperate file in a later release.
   This should help to seperate the modules and make things easier to
   understand.

 * The Rules section of lnsk.conf has been changed to Firewall4 to better
   represent the fact that it is for IPv4 firewalling only!  IPv6 firewalling
   will be in another section.  So will all the other planned features.

 * Many bugs have been fixed, mostly in the Forward and Redirect functions.
   Both of these should now work correctly with "multiport" (not "multiports").

 * I included support for the "mport" match.  If you have it, it will be used by
   default when there is a comma in your port declaration.  This will allow you
   to use commas and colons in the same declaration.

 * I am now checking to see wether or not matches are installed at the start of
   the script, instead of every time they are needed.

 * A little bit of code cleanup was done.

 * I moved the configuration help to the HELP file instead of the README.  I
   might eventually get around to making a man/info page once all of the
   configuration commands are semi-final.

[20020801-0]
 * This was the first release.  It took about a week to get this far.