[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[altq 1140] Re: parent classes with filters and priorities ?
> I'm not sure if I understand your intension but
> - in the altq filter syntax, <dest addr> comes first.
> (this might be confusing but there are historical reasons...)
> - if nge0 is an interface from edge to core, it shouldn't have
> outgoing traffic both from and to the same customer...
That was intended as you suggest, but I then realised why my config is
wrong. I have another interface which connects two independent internal
networks that I will not rate limit / QoS etc. on - and so yes, I can drop
the 'customers' class on the nge0 interface. Thanks for triggering my
thought processes ;-)
> It is described in altq-3.0/docs/TIPS.txt (or
> http://www.csl.sony.co.jp/~kjc/software/TIPS.txt) section 2.2.
OK. Interesting read.
> > Can I suggest that whoever is working on filters looks at the work done
> > recently on OpenBSD pf in case there are things there that could be used
> > the classifiers in altq ?
> Probably, we need a classifier version of ALTQ, say ALTCF :)
I always throught that a f/w filtering language is a better bet for
classification than a special parser like the one for altq.conf. Maybe there
is some mechanism that could be used to mark or classify packets in a packet
filter, like pf or ipf, that altq could then use to classify the packet into
a class ? This is probably too complex in a standalone piece of software,
but given the overall stability of the in-tree implementations of altq in
the *BSDs, there might be milage here... I am not an expert.