On 2009-05-27, irix <i...@ukr.net> wrote:
> Hello Misc,
>
> Or may be remove from altq distinguish incoming traffic or outgoing.
> What could box up to the queue as incoming and outgoing.
since queueing only happens at output, that's going to be totally
useless. it's not just a question of how altq distinguishes traffic,
you're asking to totally change how altq works.
if you have some requirement for features that altq+pf doesn't have
at the moment, you have a few choices:
- use different software that already does what you want.
- pay someone to code the features.
- code the features yourself. (if you don't code, this will require
learning how to do that first, obviously).
but, unless you want to use altq on a server (rather than a router),
there isn't really a problem with the queuing happening only on output.
just give the queues on both interfaces the same name, then you can
assign in both directions with a single rule.
stupid example ruleset. not actually tested, but I have others like
it, and it should be enough to give you the general idea.
-- -- -- -- --
altq on bge0 cbq bandwidth 4000Kb queue { normal, slow, fast }
altq on vlan5 cbq bandwidth 20000Kb queue { normal, slow, fast }
altq on vlan9 cbq bandwidth 1000Kb queue { normal, slow, fast }
queue normal bandwidth 40% priority 4 cbq(default borrow)
queue slow bandwidth 10% priority 1
queue fast bandwidth 50% priority 7
pass
pass in proto icmp queue (slow)
pass in proto tcp to port 22 queue (fast)
-- -- -- -- --
(I think some people just look at a couple of example configs which
use different queue names on interfaces and assume that it's necessary,
but it isn't).
