freebsd stable - Jun 2016 - 10.3-STABLE - PF - possible regression in pf.conf set timeout interval

On 11 May 2016 at 21:41, Luiz Otavio O Souza <loos.br at gmail.com> wrote:
> On Mon, May 9, 2016 at 12:15 PM, Kristof Provost wrote:
> >
> >> On 09 May 2016, at 16:58, Damien Fleuriot wrote:
> >>
> >> Since the upgrade, pf rules won't load anymore at boot time,
nor even
> >> manually with pfctl -f /etc/pf.conf :
> >> # pfctl -f /etc/pf.conf
> >> /etc/pf.conf:24: syntax error
> >> pfctl: Syntax error in config file: pf rules not loaded
> >>
> >> The problematic line is :
> >> set timeout interval 10
> >>
> > I think that was broken by the commit which added ALTQ support for
CoDel.
> >
> > It made ?interval? a keyword, and it looks like that breaks things for
> you.
> >
> > I?ve cced       loos so he can take a look.
>
> Damien,
>
> I was AFK in the past couple days, I'll look at this tonight.
>
> Luiz
>

Cheers Luiz,

Do tell if I may be of help, got a building box at work I can use just for
that ;)

On Wed, May 11, 2016 at 09:44:32PM +0200, Damien Fleuriot
wrote:
> On 11 May 2016 at 21:41, Luiz Otavio O Souza <loos.br at gmail.com>
wrote:
> 
> > On Mon, May 9, 2016 at 12:15 PM, Kristof Provost wrote:
> > >
> > >> On 09 May 2016, at 16:58, Damien Fleuriot wrote:
> > >>
> > >> Since the upgrade, pf rules won't load anymore at boot
time, nor even
> > >> manually with pfctl -f /etc/pf.conf :
> > >> # pfctl -f /etc/pf.conf
> > >> /etc/pf.conf:24: syntax error
> > >> pfctl: Syntax error in config file: pf rules not loaded
> > >>
> > >> The problematic line is :
> > >> set timeout interval 10
> > >>
> > > I think that was broken by the commit which added ALTQ support
for CoDel.
> > >
> > > It made ?interval? a keyword, and it looks like that breaks
things for
> > you.
> > >
> > > I?ve cced       loos so he can take a look.
> >
> > Damien,
> >
> > I was AFK in the past couple days, I'll look at this tonight.
> >
> > Luiz
> >
> 
> 
> Cheers Luiz,
> 
> Do tell if I may be of help, got a building box at work I can use just for
> that ;)
Hi,

Is there any news on this?
We hit the problem today while applying our pf.conf from a 10.2 machine to
a 10.3-STABLE.  Took a while to find out what actually happened to pf.conf
until a colleage found this thread.
	Perhaps we should open a bug report for this?

Cheers
~ollie


-- 
Oliver PETER       oliver at gfuzz.de       0x456D688F