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 10:45:13 +0000 [thread overview]
Message-ID: <marc-lartc-102189158926917@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102188660824086@msgid-missing>
> 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..
Not really. There are some other scripts, but none of them uses the output
of tc. Most of them are based on iptables counters. I'm still thinking
about rewriting my script so you can see the output of tc and also graphs
from iptables counters. And I need a better interface.
> > 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..
You have to enable it in the kernel. And you need to install the bridge
tools (I think it's called brcfg). After enabling the bridge, you have a
bridge device that forwards all traffic like a bidge and you'r done.
Filtering traffic can be done with the u32 filter.
> Queue lives on a local NT server, printer itself is JetDirect'ed.
> Workstation (and thus the ICA client) spool to the server
Can't you print directly to the JetDirect boxes from the ICA server? That
way you can easy mark the print traffic.
> > 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
--
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/
next prev parent reply other threads:[~2002-05-20 10:45 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
2002-05-20 10:45 ` Stef Coene [this message]
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-102189158926917@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 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.