* Martin Pieuchot [2018-02-23 10:04]:
> On 23/02/18(Fri) 04:08, Henning Brauer wrote:
> > * Martin Pieuchot [2018-02-21 09:37]:
> > > On 21/02/18(Wed) 02:37, Henning Brauer wrote:
> > > I'd suggest moving the pool allocation and the function in net/pf*.c
> > > and only have a function call under
On 23/02/18(Fri) 04:08, Henning Brauer wrote:
> * Martin Pieuchot [2018-02-21 09:37]:
> > On 21/02/18(Wed) 02:37, Henning Brauer wrote:
> > I'd suggest moving the pool allocation and the function in net/pf*.c
> > and only have a function call under #if NPF > 0.
>
> worth discussing, but imo that
* Martin Pieuchot [2018-02-21 09:37]:
> On 21/02/18(Wed) 02:37, Henning Brauer wrote:
> I'd suggest moving the pool allocation and the function in net/pf*.c
> and only have a function call under #if NPF > 0.
worth discussing, but imo that part doesn't really have all that much
to do with pf.
> I
On 21/02/18(Wed) 02:37, Henning Brauer wrote:
> Here comes generic delay functionality for pf.
> The manpage bits are missing for the moment, but it's really simple to
> use:
>
> match in set delay 1
>
> delay is in ms. should I change the parser to explicitely require
> "ms", as in "match in
Here comes generic delay functionality for pf.
The manpage bits are missing for the moment, but it's really simple to
use:
match in set delay 1
delay is in ms. should I change the parser to explicitely require
"ms", as in "match in set delay 1ms"?
I have a pool_sethardlimit as a "last res
