[LARTC] Prioritising Ingress Traffic

[LARTC] Prioritising Ingress Traffic

[Gordan Bobic]

Can this be done?

Provided the DS9 patch works for me, is it possible to somehow prioritize what 
is dropped first and what is dropped last? Something like attaching a 
prio/cbq to the ingress qdisc? For example, I want SSH/POP3/IMAP4 traffic to 
be dropped last, and FTP/SMTP traffic to be dropped first. Can ingress 
support in DS9 do this, or is it limited to indiscriminately dropping 
traffic?

Regards.

Gordan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Prioritising Ingress Traffic

[Julian Anastasov]

	Hello,

On Thu, 20 Mar 2003, Gordan Bobic wrote:

> Provided the DS9 patch works for me, is it possible to somehow prioritize what
> is dropped first and what is dropped last? Something like attaching a
> prio/cbq to the ingress qdisc? For example, I want SSH/POP3/IMAP4 traffic to
> be dropped last, and FTP/SMTP traffic to be dropped first. Can ingress
> support in DS9 do this, or is it limited to indiscriminately dropping
> traffic?

	Except if someone has another idea, may be only dropping.
I'm not sure there is IMQ for 2.2 :) May be you can look at
Edge31-ca-u32 from the iproute2 examples, there are some ideas
about using policers. As for DS9, it tries to provide the same
interface to all qos objects as in 2.4, so it is possible to do
the same things as in 2.4, of course, there is one problem, nobody
wants to support new features in 2.2 :)

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/