Linux Network Solution Kit README--------------------------------------------------------------------------------                                                                *** Overview ***The Linux Network Solution Kit is, as stated on the SourceForge.net summary page[http://sourceforge.net/projects/lnsk/], "An easy, yet highly-configurable iptables-based firewall solution designed for everybody from home users tonetwork admins. Functionality for IPv6, tunneling, IPSec, and advanced routingis planned."In other words, it makes setting up simple or complex networked computersrunning Linux an easy task.  In all actuality, LNSK is not limited to networkingspecific tasks; modules can be made for any task.LNSK is split up into the main executable (this package) and the differentmodules.  This package may or may not have come with some modules.  You shouldbe able to find more modules for LNSK at the same site you got this packagefrom.This README is for the main LNSK executable only.  It describes the basic layoutof the config file, basic setup, and invocation of LNSK.  For help on a specificmodule, please view the README for that package.                              *** Installation ***Run ./install.sh for a standard installation.  All this does is copy lnsk to/usr/local/bin, creates the /usr/local/lib/lnsk/modules directory, and createsan empty config file at /etc/lnsk.conf.Installing modules is also really simple once LNSK is installed to a directoryin your $PATH.  Just enter the directory with the module that you wish toinstall and type "lnsk install".  This will install every lnsk.* module in thedirectory.  You can also specify a list of modules to install with"lnsk install <filenames>".  Yes, it's that simple.                               *** Basic Setup ***LNSK is designed to be run during system startup.  This file does not go intodetails of how this is done because just about every distro seems to do it alittle bit differently.  Once you figure out how to modify the startup files,adding LNSK is easy.  LNSK can also be run from the command line.  The nextsection entitled Invocation tells how to do both of these.In order to run the basic commands (lnsk {start|stop|restart}) you must have theconfig file correct to your specific application for both the base LNSKexecutable and all of the modules' sections.  This is covered in the Config Filesection.                               *** Invocation ***There are three predefined arguments that you can supply when you use LNSK - start, stop, and restart.  These will run the start, stop, or restart functionof every configured module.  This is the most common way of using LNSK (in asystem startup/shutdown script).You can also run a single function of any module that is in the modulesdirectory.  This is done by supplying the name of the module as the firstparameter to lnsk, the name of the function you wish to run, and optionally anyarguments that the funcion takes (lnsk <module> <function> [params]).                               *** Config File ***The config file is simple - it is basicaly just a bash script that is read byLNSK every time it runs.  It covers both the configuration of the base LNSKexecutable as well as the configuration of all of the modules.  This sectiononly describes the configuration of the base.  Information of configuration ofmodules should be documented in one of the files that came with that module.Right now, the only configuration that can be done on the base is setting a fewvariables:	ECHO - The location of "echo".  The default is "echo".	SED - The location of "sed".  The default is "sed".	GREP - The location of "grep".  The default is "grep".	MESSAGES - Specify if you want to view messages or not.  "yes" is on,		anything else is off.  "yes" is the default.	MODULES_DIR - The location of the directory containing all of the modules.		The default is "/usr/local/bin/lnsk/modules".The defaults for ECHO, SED, and GREP should suit you fine as long as these arein your path at the time this script is run.                                  *** Bugs ***There is no way to specify an order to which the modules are started.  This isnot a problem right now because there is only one module, but it could be aproblem in the future.  This should be fixed in an upcoming version.