Nope, I have the top of the range 'Fully loaded' software load. There are only two software options.
When I talked to RevK about this, he pointed out that there are no queues to manage in the Friebrick, it just ships packets off to the modems as quickly as you like so egress queues never build up. Active queue management would not therefore work, that was his point. While I understand that this is literally true, it is a situation only created by the fact that the Brick is choosing to push the packets out as fast as possible, pushing problem onto the modems and is sending stuff to them faster than they can take it, despite the fact that it knows or at least can know how fast a rate the oh the modems can handle. My brick is told what the speed of each line is, in the config file. With a design change it could be set to only send packets out at a timed rate, and then manage the queue behind with intelligent modern goodness. But that would be a fair rewrite and a lot of work, also adding the potential for bugs, so designers are often loathe to risk breaking something that is currently bug free.
Given that the Brick gets told what the speed of each link is, then you might wonder what it is doing with this information. It has a speed limiter object facility, which can be used generally anywhere to cause it to drop packets. But that might mean, I think, that once again queues do not build up, and you do not have the information there in a queue to let you prioritise amongst packets. The speed rates do, I fervently hope, give the Brick an idea of how to split the load over multiple lines so that the correct fraction goes to each line, since my lines are not the same upstream speed, one is about 15% faster upstream than the other two, for some reason.
I think it is worth doing the full thing though, as proper QoS is a really big deal for me. I mean both in terms of observing L2 and L3 QoS fields and possibly marking them by actually modifying the QoS fields, and also regarding the possibility of declaring ad-hoc rules to add QoS handling instructions to different types of traffic according to various categorisation strategies. Examples: things like prioritising all small packets, all DNS, all TCP ACKs. These traffic categories could then be assigned to queues possibly overriding the QoS markings or being placed into sub-queues at the next level below.
I wonder if any really fancy switches can do this kind of really good QoS categorisation and re-queuing? Again I would run into the problem of it simply not working if the switch just ships all packets to the Brick as fast you like. Anyway, if there is such a device, that would be a plan B if I fail yet again to persuade RevK.