rTables for Linux

Special Notice:

• I may write a new version of a rTables sometime in the future. The new feature will be far more modular. This will allow for a dynamic number of interfaces each with their own configuration.

• rTables is a detailed, custom, iptables ruleset.

• rTables was written primarally for security reasons and it's main purpose is firewalling (with or without NAT). The tables are easily defined via user settable variables, thus making rTables very easy to configure. rTables also contains support for an "untrusted" LAN and/or a "trusted" DMZ.

• rTables is currently made up of a few simple bash scripts.

• rTables is currently written to use bash & iptables on Linux v2.4.x.
• rTables has been tested under the following configurations:
  • SuSE v7.1, bash v2.04, iptables v1.2.2, Linux v2.4.5, rTables v1.06.14.0
  • SuSE v7.1, bash v2.04, iptables v1.2, Linux v2.4.2, rTables v1.03.29.0
  • RedHat v7.0, bash v2.04, iptables v1.1.1, Linux v2.4.1, rTables v1.02.27.0
  • Mandrake v7.2, bash v2.04, iptables v1.2, Linux v2.4.2, rTables v1.02.27.0
• rTables also makes use of: cut, echo, grep, & ifconfig.

• rTables development has stopped.

• rTables can be found at: no longer available
• MD5Sum's can be found at: http://rtables.rebby.com/md5sums.html.

• FAQ
• Changelog
• MD5Sum's.

• Support is no longer available

• Version numbering uses a date/revision stamp in the format: Y.MM.DD.R (year - month - day - revision).
• I use the term "stable" loosely since this firewall script is not going to crash your system unless something is very wrong with your system already. A stable release simply indicates that at the time of release there were no known bugs in the script. Unstable (devel) releases may contain bugs; if you use an unstable release (or even a stable one), please report back any problems you encounter and/or desired functionality.
• To find out what version of rTables you are currently running do: `/etc/rTables/bin/rTables.sh -version` or view the top few lines of `/etc/init.d/rTables status`.

• Improve FAQ.
• "Finish" code.
• Implement transparent proxy support.