On 03/24/10 06:38 AM, Paul Wernau wrote:
> I remember this scenario coming up when we were creating this location.
> For consistency with customizations we'd usually just give you a
> variable to formally define your ipfilter policy.
>
> e.g. PUNCHIN_IPFILTER_POLICY=/path/to/my/policy/file
>
> Would that be acceptable? Destroying it is a much simpler and cleaner
> method since the location is dynamically pieced together depending on
> other variables anyway, such as whether you want NIS, custom resolv.conf
> domains, etc. An IPfilter variable would fit into that scheme fairly
> well, it seems to me.
If you look at NWAM there are 4 files it exposes (ipf6, ipf, ipnat,
ippool) so for completeness it would make sense to define all 4 in the
customization file.
Erik
