From: "Michael McTernan" <Michael.McTernan.2001@cs.bris.ac.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] CQB & links of varying capacity
Date: Wed, 14 Nov 2001 21:03:21 +0000 [thread overview]
Message-ID: <marc-lartc-100577169624524@msgid-missing> (raw)
Hi,
I've been reading lots of documents and examples of setting up traffic
shaping, and found that they _all_ refer to specific bandwidths for queues.
I am using a dialup connection, and therefore can connect at different
rates, and also have a dynamically changing 'bandwidth' dependent on
compression.
What I want to do is to specify that interactive traffic (telnet, ftp
commands etc...) should be sent before anything else, without worrying about
how much bandwidth to allocate to what.
I'm just wondering if the current traffic shaping is workable for my
problem, or whether I am forced to try specifying Mbits everywhere when it
doesn't really make sense(?).
cheers,
Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-11-14 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100577169624524@msgid-missing \
--to=michael.mcternan.2001@cs.bris.ac.uk \
--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