| 1 | # Configuration for blastfw |
|---|
| 2 | |
|---|
| 3 | # $Id: config.blast,v 1.1.1.1 2004/08/31 13:33:28 thomasez Exp $ |
|---|
| 4 | |
|---|
| 5 | # |
|---|
| 6 | # Fill in the blanks. |
|---|
| 7 | # |
|---|
| 8 | |
|---|
| 9 | # For configuring of modules to use, |
|---|
| 10 | # this includes the network interfaces: /modules.lst |
|---|
| 11 | |
|---|
| 12 | # For configuring extra network interfaces and firewall rules |
|---|
| 13 | # you may use network.ini |
|---|
| 14 | |
|---|
| 15 | # |
|---|
| 16 | # Physical device layout: |
|---|
| 17 | # |
|---|
| 18 | # In the files /etc/outside.info and /etc/inside.info you will see |
|---|
| 19 | # OUTSIDDE_DEVICE and INSIDE_DEVICE, those are the logical devices used by |
|---|
| 20 | # firewall.init and friends.. |
|---|
| 21 | # |
|---|
| 22 | # If you have only one network card you can set INSIDE_DEV to eth0:0 |
|---|
| 23 | # and it will use ip aliasing to make it all work. |
|---|
| 24 | # |
|---|
| 25 | OUTSIDE_DEV=eth0 |
|---|
| 26 | INSIDE_DEV=eth1 |
|---|
| 27 | |
|---|
| 28 | # |
|---|
| 29 | # Password can be created in many ways. Youhave two (three) options, |
|---|
| 30 | # DES_PASSWORD will accept a crypted strong |
|---|
| 31 | # PASSWORD will accept a strong (the specific root password). |
|---|
| 32 | |
|---|
| 33 | # This will give you "ffw" as login password. |
|---|
| 34 | # DES_PASSWORD=nCLm5JgCK0G5U |
|---|
| 35 | PASSWORD= |
|---|
| 36 | |
|---|
| 37 | # |
|---|
| 38 | # Done! Your blastfw should already work by now. |
|---|
| 39 | # Save this file and give it a shot ! |
|---|
| 40 | # |
|---|
| 41 | #============================================================================= |
|---|
| 42 | |
|---|
| 43 | |
|---|
| 44 | |
|---|
| 45 | #----------------------------------------------------------------------------- |
|---|
| 46 | |
|---|
| 47 | # |
|---|
| 48 | # Defaults and switches: |
|---|
| 49 | # |
|---|
| 50 | |
|---|
| 51 | HOSTNAME=blastfw |
|---|
| 52 | DOMAIN=blastfw.com |
|---|
| 53 | |
|---|
| 54 | # |
|---|
| 55 | # And for the logging the scripts use: |
|---|
| 56 | # Default works for most purposes. |
|---|
| 57 | # |
|---|
| 58 | DEBUG_LOG="/dev/vc/3" |
|---|
| 59 | |
|---|
| 60 | # |
|---|
| 61 | # Turning on syslogd and klogd. |
|---|
| 62 | # This is a nice thing but will eat CPU which is why it is turned |
|---|
| 63 | # off by default. |
|---|
| 64 | # The firewall.ini file is where you can turn on logging of rejected packages. |
|---|
| 65 | # |
|---|
| 66 | USE_SYSLOG=n |
|---|
| 67 | |
|---|
| 68 | # Uncomment to log to /dev/vc/4 instead of /var/log/messages |
|---|
| 69 | # which aren't exactly a good idea on a ramdisk. |
|---|
| 70 | SYSLOG_TTY="-O $DEBUG_LOG" |
|---|
| 71 | # Or the another virtual console than the other messages: |
|---|
| 72 | # SYSLOG_TTY="-O /dev/vc/4" |
|---|
| 73 | |
|---|
| 74 | # Uncomment to log to network. host:port |
|---|
| 75 | # SYSLOG_NET="-R 10.42.42.42:514" |
|---|
| 76 | |
|---|
| 77 | # Uncomment to not print a mark |
|---|
| 78 | # SYSLOG_MARK="-m 0" |
|---|
| 79 | |
|---|
| 80 | [ "$SYSLOG_TTY" -a "$SYSLOG_NET" ] && SYSLOG_BOTH="-L" |
|---|
| 81 | SYSLOG_FLAGS="$SYSLOG_MARK $SYSLOG_TTY $SYSLOG_NET $SYSLOG_BOTH" |
|---|
| 82 | |
|---|
