From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] 'tc' locked my machine...
Date: Fri, 07 Mar 2003 02:13:49 +0000 [thread overview]
Message-ID: <marc-lartc-104700259809771@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104696198821253@msgid-missing>
Tc qd del dev eth1 root
Will do the trick. Take the wondershaper script from the lartc site. It
handles exactly whawt you have in mind.
Mohan
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of Ben Clewett
Sent: Thursday, March 06, 2003 8:09 PM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] 'tc' locked my machine...
Newbe...
I am following the Linux Advanced Routing & Traffic Control HOWTO, as I
am having difficulty with a satelite ADSL connection.
Section 9.2.2.2 describes a case identicle to mine, and surgests
throttle using 'tc'. On a test machine I entered:
# tc qdisc add dev eth1 root btf rate 64kbit latency 50ms burst 1500
When I enter 'tc qdisc show' I get:
disc tbf 8001: dev eth1 rate 64Kbit burst 1499b lat 60.9ms
But, I now find my ftp failes. In either direction. It creates a file
of 0 bytes, then stalles for ever more.
Also I have no 'man tc' and I can't remove this entry in any logical way
(like with 'tc qdisc del dev eth1') I can think of.
Can anybody please let me know how I get ftp to work with the Token
Bucket Filter, and how to remove the entry once it's been entered...
Thanks greatly in advance,
Ben
PS, kernel 2.4.19
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-07 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 14:38 [LARTC] 'tc' locked my machine Ben Clewett
2003-03-07 2:13 ` S Mohan [this message]
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-104700259809771@msgid-missing \
--to=smohan@vsnl.com \
--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.