All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bas Rijniersce" <bas@brijn.nu>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Limiting Citrix printing traffic, so ensure interactive sessions
Date: Mon, 20 May 2002 09:58:39 +0000	[thread overview]
Message-ID: <marc-lartc-102188876925214@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102188660824086@msgid-missing>

Hi,

> From: Stef Coene [mailto:stef.coene@docum.org] 

Very good page by the way! Your page was the first I found when
searching for linux and QoS.. Side note, do you have any other links to
graphing tools for the "controlled" traffic. For us it will be very
helpful to see how much traffic was passed/limited etc..

> Why proxy arping?  You can enable briding so the network 
> don't know you are 
> shaping.  If there is a problem with the brdige, just remove 
> it and you can 
> work again.

Because I don't know exactly how a bridge is build :-) But I'll read up
on that..
 
> > It seems that Citrix traffic uses dynamic port numbers so 
> identifying 
> > them this way seems impossible. If someone knows a way to 
> use the u32 
> > filter to select Citrix normal and Citrix printing traffic???

> How do you print?  To dedicated print-servers or to printers 
> attached to 
> windows boxes?

Queue lives on a local NT server, printer itself is JetDirect'ed.
Workstation (and thus the ICA client) spool to the server
 
> > The behaviour that I would like to get:
> > - If no other traffic, printing or interactive get 100%
> > - If other traffic, printing gets the rest
> >
> > I don't know if this is possible, acceptable would also be, let 
> > printing never exceed 30% of the total bandwidth

> Very easy to implement it in CBQ or HTB.  The most difficult part is 
> separating the printing traffic and the citrix traffic.

But I think we have the IP space in the office to split a small subnet
of for printers, that would solve this problem I guess
 
> Stef

Bas

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

  parent reply	other threads:[~2002-05-20  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20  9:23 [LARTC] Limiting Citrix printing traffic, so ensure interactive sessions Bas Rijniersce
2002-05-20  9:48 ` Stef Coene
2002-05-20  9:58 ` Bas Rijniersce [this message]
2002-05-20 10:45 ` Stef Coene
2002-05-20 12:29 ` Thomas Graf
2002-05-20 12:40 ` Stef Coene

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=marc-lartc-102188876925214@msgid-missing \
    --to=bas@brijn.nu \
    --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.