On Wed, 2003-02-19 at 17:40, Jason Dixon wrote:
> On Wed, 2003-02-19 at 15:06, Henning Brauer wrote:
> > > >I assumed it was due to the expansion "($int_if)/24", so I tried with a
> > > >single IP, and that fixed it. What is the new syntax like for cidr
> > > >expansion on an interface? I can't find any examples in the manpage.
> > > >
> > > $int_if:network probably
> >
> > well, of course that works fine, and of course $int_if/24 does too, but
> > ($int_if)/24 does _not_.
> > did that EVER work correctly?
> > off to check pf.c ...
>
> As mentioned previously, yes, this worked with 3.2 -release and
> -stable. Now that I think about it, the dynamic syntax () isn't even
> necessary on THAT interface, but I can see other instances where it
> might be. Are you saying that interface macros now support dynamic
> updates by default? If not, which syntax does? Forgive me if it's in
> the manpage, I can't find it.
Sorry to self-post, but I did find that the syntax ($int_if:24) does
indeed work. The manpage mentions...
"When the interface name is surrounded by parentheses, the rule is
automatically updated whenever the interface changes its address. The
ruleset does not need to be reloaded."
I'm probably splitting hairs, but this sounds a little ambiguous with
respect to interface modifiers. Nothing a little testing can't solve,
but...
If I knew how to correctly create a diff, I'd be happy to submit doc
patches. {wink}
-J.
