Technical data

8. Documentation for Developers
# extension is available
foo_p=yes
# the actual extension, adding matches to match_opt
do_foo()
{
param=$1
get_negation $param
match_opt="$match_opt -m foo $neg_opt --fooval $param"
}
2. Testing the extension:
$ cd opt/etc/rc.d
$ sh test-rules.sh 'foo:bar ACCEPT'
add_rule filter FORWARD 'foo:bar ACCEPT'
iptables -t filter -A FORWARD -m foo --fooval bar -s 0.0.0.0/0 \
-d 0.0.0.0/0 -m comment --comment foo:bar ACCEPT -j ACCEPT
3. Adding the extension and all other needed files (iptables components) to the archive
using the known mechanisms.
4. Allowing the extension in the configuration by extending of FW_GENERIC_MATCH in an exp-
file, for example:
+FW_GENERIC_MATCH(OPT_FOO) = 'foo:bar' : ''
8.6. CGI-Creation for Package httpd
8.6.1. General information about the web server
The web server used in fli4l is mini_httpd by ACME Labs. The sources can be found
at http://www.acme.com/software/mini_httpd/. However, a few changes in the current ver-
sion were made for fli4l. The modifications are located in the src package in the directory
src/fbr/buildroot/package/mini_httpd.
8.6.2. Script Names
The script names should be self-explanatory in order to be easy to distinguish from other
scripts and even similar names have to be avoided to differ from other OPTs.
To make scripts executable and convert DOS line breaks to UNIX ones a corresponding
entry has to be created in opt/<PACKAGE>.txt, see Table 8.2 (Page 289).
8.6.3. Menu Entries
To create an entry in the menu you have to enter it in the file /etc/httpd/menu. This
mechanism enables OPTs to change the menu during runtime. This should only be done using
the script /etc/httpd/menu because this will check for valid file formatting. New menu items
are inserted as follows:
323