In article <44B3E8E9.1080500@gmail.com>,
Mark Cullen  <mark.r.cullen@gmail.com> wrote:
>Jeff Rizzo wrote:
>> Mark Cullen wrote:
>>> I've got PF in my kernel config and the kernel compiled just fine, but
>>> I would like to mess around with ALTQ. When I uncomment the ALTQ lines
>>> in the kernel config, the compiling fails with:
>>>
>> <snip>
>>> I think it's a known problem. A google search revealed patches to fix
>>> it for 2.x, but I am using 3.0.1.. and they're reported not to work on
>>> 3.x apparently. Any ideas?
>> 
>> Yes, it's a known problem.  There are unsupported patches that should
>> work for 3.0 (and 3.0.1), and the problem itself is being worked on; 
>> it's unclear whether it will be supported in 4.0 or not.
>> 
>> +j
>> 
>> 
>> 
>
>Oh. What's taking it's place if it's not supported in 4.0? Just no 
>ability to do traffic shaping at all?

The patches are in a branch right now and they are being worked on.
They should be integrated in time for 4.0. If they are not, this
means no traffic shaping with pf+altq, but you should be able to
use altq separately (without using pf).

christos