From: Bill Gradwohl <bill@ycc.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking passive ftp and shaping
Date: Sun, 08 Aug 2004 15:23:13 +0000 [thread overview]
Message-ID: <41164561.9070001@ycc.com> (raw)
In-Reply-To: <411289DB.8020500@cfl.rr.com>
nix4me wrote:
> It is not working correctly, it seems to limit ALL traffic. Cant file
> share or anything.
>
I'm new to traffic control, so maybe I shouldn't try to help, but you
only have 1 qdisc DEFINED to service the device. You also don't specify
a default via that definition.
According to http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm - Now
we can optionally attach queuing disciplines to the leaf classes. If
none is specified the default is pfifo.
This seems to say that you get another qdisc for your one and only
class, but where is your other traffic going? That same site shows
examples that don't rely on defaults. Maybe you should consider stating
explicitely what you want as the defaults the system is giving you may
be your problem.
--
Bill Gradwohl
bill@ycc.com
http://www.ycc.com
SPAMstomper Protected email
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-08 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 19:26 [LARTC] marking passive ftp and shaping nix4me
2004-08-08 15:23 ` Bill Gradwohl [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=41164561.9070001@ycc.com \
--to=bill@ycc.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.