nginx + DSCP (Differentied services)

[Dani Bento]

Hello,

Any advance on this idea? Or it will be easier to adapt
Maxim's module to do what we want? (mainly IPv6 compatibility and the
possibility to change DSCP mark via backend header interaction).

Thanks.
Dani

On Wed, 17 Dec 2014 11:27:29 +0000
Dani Bento <dani at telecom.pt> wrote:

> Hello,
> 
> In attachment is our patch to the nginx core. You can take a look.
> 
> We found that your module isn't IPv6 compatible too, but it may be
> simple to implement that.
> 
> Thanks.
> 
> On Tue, 16 Dec 2014 18:48:28 +0000
> Maxim Dounin <mdounin at mdounin.ru> wrote:
> 
> > Hello!
> > 
> > On Tue, Dec 16, 2014 at 05:24:42PM +0000, Dani Bento wrote:
> > 
> > > Thanks for the reply.
> > > 
> > > We looked at your module and found it interesting that you
> > > avoided to change the core.
> > > 
> > > Our code marks each buffer flush individually. We can control the
> > > ToS for each request even when using keep-alive (using the
> > > X-Accel-ClassID header). After the response has been sent the ToS
> > > is reset back to the default (location configuration).
> > > 
> > > In your module you mark only at the beginning of the response (at
> > > the header filter stage). Don't you have problems with different
> > > requests using the same connection?
> > 
> > If you want ToS to be reset, you can use "ip_tos 0x00;" by 
> > default, see example here:
> > 
> > http://mdounin.ru/hg/ngx_http_ip_tos_filter_module/file/tip/README
> > 
> > > You can only have one ToS mark for
> > > each location if you relying on a static configuration. Can it be
> > > set by variable "tos $class_id" ?
> > 
> > Not now, but this can be added if needed - like it was recently 
> > added to the "expires" directive, see 
> > http://hg.nginx.org/nginx/rev/4983f7d18fe3.
> > 
> 
> 
> 



-- 
Dani Bento
Direção de Internet e Tecnologia
DTS/DVS
tlm: +351 91 429 72 81
dani at telecom.pt