brielle
/
SRFirewall
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

master
bbruns 2014-04-12 18:12:51 +00:00
parent 2453735f25
commit 3c1ca3ffe8
1 changed files with 31 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
INSTALL
View File

@ -4,42 +4,46 @@ Brielle Bruns <bruns@2mbit.com>
Installing is fairly straight forward: Installing is fairly straight forward:
1. Download to a location of your choosing, I recommend /usr/src 1. Download to a location of your choosing, I recommend /usr/src 2. Run
2. Run 'make install' to put files in /usr/local by default 'make install' to put files in /usr/local by default 3. Edit config
3. Edit config files in /usr/local/etc/srfirewall files in /usr/local/etc/srfirewall 4. Run 'srfirewall' command to load
4. Run 'srfirewall' command to load the firewall and work its magic the firewall and work its magic
If you are upgrading from a previous version and don't want to overwrite If you are upgrading from a previous version and don't want to overwrite
your config files, use 'make upgrade'. your config files, use 'make upgrade'.
If you wish to install to some place other then /usr/local, you will need If you wish to install to some place other then /usr/local, you will
to edit the Makefile PREFIX as well as the bin/srfirewall script to reflect need to edit the Makefile PREFIX as well as the bin/srfirewall script to
the new location. reflect the new location.
If you want to run from SVN trunk (for the brave), here's how I would do it: If you want to run from SVN trunk (for the brave), here's how I would do
it:
=== Begin commands === === Begin commands === cd /usr/src svn checkout
cd /usr/src http://firewall-sosdg.googlecode.com/svn/srfirewall srfirewall-trunk ln
svn checkout http://firewall-sosdg.googlecode.com/svn/srfirewall srfirewall-trunk -s /usr/src/srfirewall-trunk/lib /usr/local/lib/srfirewall ln -s
ln -s /usr/src/srfirewall-trunk/lib /usr/local/lib/srfirewall /usr/src/srfirewall-trunk/bin/srfirewall /usr/local/bin/srfirewall cp -R
ln -s /usr/src/srfirewall-trunk/bin/srfirewall /usr/local/bin/srfirewall /usr/src/srfirewall-trunk/etc /usr/local/etc/srfirewall === End commands
cp -R /usr/src/srfirewall-trunk/etc /usr/local/etc/srfirewall ===
=== End commands ===
Then when you want to update to bleeding edge, all you have to run is 'svn update'. Then when you want to update to bleeding edge, all you have to run is
'svn update'.
You _will_ need to look for newly changed/added files and update appropriately. You _will_ need to look for newly changed/added files and update
appropriately.
To make the update process easier, I made the config script look for a local.conf file in To make the update process easier, I made the config script look for a
etc/srfirewall that can be used to override the default options. This will allow local.conf file in etc/srfirewall that can be used to override the
you to replace all of the *.conf files on upgrade without losing local option changes. default options. This will allow you to replace all of the *.conf files
on upgrade without losing local option changes.
The default options are designed to be 'sane' for a good portion of the many users, The default options are designed to be 'sane' for a good portion of the
so the use of local.conf only needs specific options you wish to override. many users, so the use of local.conf only needs specific options you
wish to override.
Files in etc/srfirewall/ipv{4,6} can be safely left alone during upgrade since Files in etc/srfirewall/ipv{4,6} can be safely left alone during upgrade
I plan to not make upstream changes to them once they are written and defined since I plan to not make upstream changes to them once they are written
for use. and defined for use.
When in doubt, check the CHANGELOG file for mention of new config options and/or When in doubt, check the CHANGELOG file for mention of new config
config files. options and/or config files.