From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DSCP, ToS and Egress
Date: Wed, 16 Feb 2005 14:17:06 +0000 [thread overview]
Message-ID: <3063e50502160617dbcaac1@mail.gmail.com> (raw)
In-Reply-To: <20050215185238.7l3y0cr6q048k00g@home.wep.net>
You can try with IMQ, which probably is not wanted for a production
server. You can also mark the pachets which have some DSCP bits, then
use u32 with the mark match (Probably Catalin's implementation), i
think it is even in some latest 2.6 kernels, also don't forget to use
a new iproute2 :)
On Wed, 16 Feb 2005 11:12:46 +0200 (EET), Catalin(ux aka Dino) BOIE
<util@deuroconsult.ro> wrote:
> On Tue, 15 Feb 2005, Dan Cox wrote:
>
> > I'm successfully using HTB + GRED to shape traffic based on the DSCP field. I
> > would like to strip the DSCP and possibly replace it with normal ToS bits on
> > egress traffic leaving my network. Leaving DSCP set is pointless, and could
> > potentially cause problems with some ISPs that use DSCP internally I suppose.
> > Setting ToS bits would seem ideal as most networks still honor it to varying
> > degrees.
> >
> > The problem is I can see no way of doing this. Since DSCP is needed in the
> > qdiscs for shaping, it can't be mangled with iptables. According to the packet
> > flow diagram, there doesn't appear to be any other opportunity to mangle the
> > packets in this manor. Will I need to insert another router in the chain just
> > to do this? :(
>
> You can clone the GRED qdisc code and modify it to overwrite the DSCP
> bits.
>
> >
> > --
> > Dan-
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
>
> ---
> Catalin(ux aka Dino) BOIE
> catab at deuroconsult.ro
> http://kernel.umbrella.ro/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-02-16 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 0:52 [LARTC] DSCP, ToS and Egress Dan Cox
2005-02-16 9:12 ` Catalin(ux aka Dino) BOIE
2005-02-16 14:17 ` George Alexandru Dragoi [this message]
2005-02-16 15:30 ` Dan Cox
2005-02-17 10:33 ` Antonios Halkiopoulos
2005-02-17 15:33 ` Dan Cox
2005-02-17 15:50 ` Antonios Halkiopoulos
2005-02-17 17:14 ` Dan Cox
2005-02-18 17:25 ` Dan Cox
2005-10-20 11:07 ` Jonathan Lynch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3063e50502160617dbcaac1@mail.gmail.com \
--to=waruiinu@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.