Re: A detail about pf.conf

2016-10-30 Thread Peter N. M. Hansteen
On 10/30/16 01:46, Nicolai wrote: > BTW, there are generally better options for handling bruteforce > traffic. What kind of bruteforce traffic are you trying to stop? In the classic case of rapid-fire bruteforcers an adaptive, state tracking based approach such as [1] works quite well. However

Re: A detail about pf.conf

2016-10-29 Thread Nicolai
On Sat, Oct 29, 2016 at 04:48:51PM +0200, Walter Alejandro Iglesias wrote: > Any of these syntax examples return errors: > > blockIP="/path/to/file" > blockIP=/path/to/file > table persist file "$blockIP" Maybe I misunderstand what you're trying to do, but try this instead: table

A detail about pf.conf

2016-10-29 Thread Walter Alejandro Iglesias
I post this here because I don't know if considering it bug. To use a macro in the "file" table option I had to enclose double on single quotes: blockIP='"/path/to/file"' table persist file $blockIP Any of these syntax examples return errors: blockIP="/path/to/file"