>>> Greetings,
>>>
>>> I tried setting up the following into pf.conf on both 4.9 and latest
snapshot:
>>>
>>> altq on $ext_if priq queue {q1, q2}
>>> queue q1 priority 1 priq(default)
>>> queue q2 priority 2
>>> pass all queue q1
>>> match all queue q2
>>>
>>> And I see nothing going into q2.
>>> Is this the expected behavior?
>>>
>>> Thanks for your time.
>>> William
>>>
>>
>>After further experimentation, I found out the following:
>>
>>"match queue" overrides:
>> - a previous "match queue" assignment
>> - the default queue
>>
>>but does not override:
>> - a previous "pass queue" assignment
>> - a previous "block queue" assignment
>>
>>It seems to me this might not be the expected behavior, so well, I
>>thought it might be worth reporting...
>
> man 5 pf.conf:
>
> "match
> The packet is matched. This mechanism is used to provide
> fine
> grained filtering without altering the block/pass state of a
> packet. match rules differ from block and pass rules in
> that
> parameters are set every time a packet matches the rule, not
> only
> on the last matching rule. For the following parameters,
> this
> means that the parameter effectively becomes ``sticky''
> until
> explicitly overridden: nat-to, binat-to, rdr-to, queue,
> rtable, and
> scrub."
>
> R/
Rod,
Obviously I have read this part (many times). But I don't think it
implies that "pass/block queue" assignments cannot be overridden by a
"match queue" assignment. I would say it almost suggests the opposite
actually.
William
