All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] classification of incoming traffic with tc
@ 2007-06-26 17:16 Tim Enos
  2007-06-26 17:24 ` Daniel Harold L.
  2007-06-26 18:38 ` Tim Enos
  0 siblings, 2 replies; 3+ messages in thread
From: Tim Enos @ 2007-06-26 17:16 UTC (permalink / raw)
  To: lartc

Hi all,

Another requirement we have is that traffic entering the DS domain be
classified then subsequently assigned a (different?) DSCP based upon its
classification.

For illustrative purposes only let's say (for traffic entering the DS domain
on dev eth0):

- WWW traffic would be marked BE

- traffic destined for 10.10.10.10 would be marked AF11

- VoIP traffic from 20.20.20.20 would be marked EF

- packets 500 bytes in length would be marked AF22

I'm looking for the Linux router to classify and mark the incoming traffic,
_not_ the originating host(s). From what I can see, dsmark only works on
egress qdiscs (is this indeed the case?). I need something that works on an
ingress (qdisc?). 

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [LARTC] classification of incoming traffic with tc
  2007-06-26 17:16 [LARTC] classification of incoming traffic with tc Tim Enos
@ 2007-06-26 17:24 ` Daniel Harold L.
  2007-06-26 18:38 ` Tim Enos
  1 sibling, 0 replies; 3+ messages in thread
From: Daniel Harold L. @ 2007-06-26 17:24 UTC (permalink / raw)
  To: lartc

On Wednesday 27 June 2007 01:16, Tim Enos wrote:

> I'm looking for the Linux router to classify and mark the incoming traffic,
> _not_ the originating host(s). From what I can see, dsmark only works on
> egress qdiscs (is this indeed the case?). I need something that works on an
> ingress (qdisc?).

afaik, you can use IMQ or IFB for ingress qdisc.

Daniel
PadiNet Makassar
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [LARTC] classification of incoming traffic with tc
  2007-06-26 17:16 [LARTC] classification of incoming traffic with tc Tim Enos
  2007-06-26 17:24 ` Daniel Harold L.
@ 2007-06-26 18:38 ` Tim Enos
  1 sibling, 0 replies; 3+ messages in thread
From: Tim Enos @ 2007-06-26 18:38 UTC (permalink / raw)
  To: lartc

Hi Daniel,

Thanks. So how exactly would I use either IMQ or IFB to classify and
subsequently mark incoming traffic with a (new) DHCP?

If you have a configuration example, that would be most helpful.

> -----Original Message-----
> From: lartc-bounces@mailman.ds9a.nl [mailto:lartc-bounces@mailman.ds9a.nl]
> On Behalf Of Daniel Harold L.
> Sent: Tuesday, June 26, 2007 1:24 PM
> To: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] classification of incoming traffic with tc
> 
> On Wednesday 27 June 2007 01:16, Tim Enos wrote:
> 
> > I'm looking for the Linux router to classify and mark the incoming
> traffic,
> > _not_ the originating host(s). From what I can see, dsmark only works on
> > egress qdiscs (is this indeed the case?). I need something that works on
> an
> > ingress (qdisc?).
> 
> afaik, you can use IMQ or IFB for ingress qdisc.
> 
> Daniel
> PadiNet Makassar
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-06-26 18:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-26 17:16 [LARTC] classification of incoming traffic with tc Tim Enos
2007-06-26 17:24 ` Daniel Harold L.
2007-06-26 18:38 ` Tim Enos

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.