Stijn Jonker wrote:
What do you all think, is this an usefull addition? If so i'll see if i
can get a patch ready over the (long easter) weekend.
I favor a different approach and would have done it if I would have
thought of it before 2.0.0-RC1 was out. We discussed it on the LEAF
development
Stijn Jonker wrote:
Tom,
But when heavily using actions, it still means a somewhat cluttered
shorewall directory, the following files are modified on my install (rpm
-q --verify shorewall)
S.5T c /etc/shorewall/actions
S.5T c /etc/shorewall/interfaces
S.5T c /etc/shorewall/masq
S.5.
Tom Eastep wrote:
Ok -- how about a CONFIG_SEARCH option in shorewall.conf:
For compatibilty, the default value is:
$SHOREWALL_DIR:/etc/shorewall/:/usr/share/shorewall
SHOREWALL_DIR is the configuration directory specified by the -c command
option or named explicitly in the 'try' command.
Tom Eastep wrote:
The nice thing about this proposal is that I could implement it now in a
minor release and we could hold off until next year to implement the
more radical proposal (no files released directly to /etc/shorewall).
The code in CVS (Shorewall2/) supports this notion. Be sure to ch
