[Shorewall-users] Feature Request: Shorewall 2.0 LocalConfDir

Stijn Jonker SJCJonker at SJC.nl
Fri Apr 9 13:38:41 PDT 2004


Tom,

sounds wonderfull to me!

Tom Eastep said the following on 09-04-04 22:34:
> 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.5....T c /etc/shorewall/actions
>> S.5....T c /etc/shorewall/interfaces
>> S.5....T c /etc/shorewall/masq
>> S.5....T c /etc/shorewall/modules
>> S.5....T c /etc/shorewall/params
>> S.5....T c /etc/shorewall/policy
>> S.5....T c /etc/shorewall/routestopped
>> S.5....T c /etc/shorewall/rules
>> S.5....T c /etc/shorewall/shorewall.conf
>> S.5....T c /etc/shorewall/tunnels
>> S.5....T c /etc/shorewall/zones
>>
>> Now add the 18 Actions (Services in my case) and rfc1918 (need to 
>> exclude one /24 in 192.168), bogons (stupid allocation in friendly 
>> net) would still leave me with 31 config files in /etc/shorewall maybe 
>> both is an option? (or /etc/shorewall/actions) only?
>>
> 
> 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

-- 
Met Vriendelijke groet/Yours Sincerely
Stijn Jonker <SJCJonker at sjc.nl>


More information about the Shorewall-users mailing list