Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Limiting Citrix printing traffic, so ensure interactive sessions
Date: Mon, 20 May 2002 09:48:56 +0000	[thread overview]
Message-ID: <marc-lartc-102188817124871@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102188660824086@msgid-missing>

On Monday 20 May 2002 11:23, Bas Rijniersce wrote:
> LS,
>
> Spent a lot of this weekend reading about shaping and traffic control.
> The Howto is very extensive... :-) I hope to use this list to see if
> what I want is possible.
>
> The situation:
> - A central (big) Citrix cluster located in Frankfurt (all servers in
> one subnet)
> - The office in Rotterdam connected to Franfurt with a 2Mbit line
> - The office in Bergen (Norway) connected to *Rotterdam* with a 128 line
>
> Normal citrix session uses max 20k/s, printing is not limited! The
> problem is obvious, one user sent a big print job... Away is the
> interactive performance..
>
> What i'm thinking of:
>
> [Citrix cluster] -- [Linux proxy-arp shaper]-- Router to RTD -- Router
> to Brg
>
> What is probably very easy to do is bring all the printers in a separate
> subnet in Bergen and use iptables to mark the packets for this subnet (I
> build a proxy-arp firewall before, so these are familiair techniques).
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.

> 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?

> 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.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2002-05-20  9:48 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 [this message]
2002-05-20  9:58 ` Bas Rijniersce
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-102188817124871@msgid-missing \
    --to=stef.coene@docum.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox