Stuart Remphrey wrote:
> Hi Darren, David, et al,
>
> Very nifty idea -- would make related/complex
> application port usage simpler & more efficient.
>
>
> Somewhat vaguely related:
>
> Is there any interest out there in a nested "include"
> facility for *.conf files?
>
> Would be useful for common variable definitions,
> e.g. assuming file "our_ips.conf" contained:
> dbip=w.x.y.z/32;
> webfarmip=a.b.c.d/28;
> then one could have organisation-wide or application
> specific rule-sets in other include files, e.g. webapp.conf:
> include our_ips.conf;
> pass in on $int proto tcp from $webfarmip to any port 1521 flags S/SAFR
> keep state keep frags
> pass out from $(dbip) to any
> which would be included by the server-specific file:
> int=bge0;
> include webapp.conf;
> ...
> or whatever.
>
For addresses, I think you want to do:
table role = ipf type=tree number=100 {
file:///etc/ipf/webapp-ipaddr.conf;};
..but this was added in for 4.1.14.
> While off the topic and onto IPF variables/macros,
> allowing underscores in the grammar for pool and
> variable names would be a nice touch.
>
Hmm, that should be easy :)
Cheers,
Darren
