Kenneth Gober wrote: > On Wed, Feb 5, 2020 at 3:01 PM Michael Glasgow <[email protected]> wrote: > > I've seen some mention that one should avoid using "quick" in > > complex rulesets, but I'm not sure why. I suspect there is some > > rule of thumb that I'm missing? > > I suspect this advice was actually intended to be that you should either > use "quick" all the time, or never. In other words, use it consistently. .. > I always use quick and I think it makes my rulesets clearer, because I > personally find "first match" to be easier to reason about.
Thanks! Sounds like we're pretty much on the same page, which is reassuring. I was accustomed to first-match from previous solutions, so I just carried over that practice to pf without thinking too much about it. Recently I'd begun to wonder if there was perhaps some actual reason that pf was designed to be last-match by default, and it made me wonder if there was some perspective I'd never considered. It's always interesting when someone can make a compelling case that "you're doing it wrong", and show you that the tool you're using was designed to be used in a different way than you're accustomed. But perhaps last-match is only a "default" for some reason relating to syntax, and it wasn't necessarily intended to imply a preference for how rules are written? -- Michael Glasgow <[email protected]>
