From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC and prioritization
Date: Fri, 12 May 2006 16:42:34 +0000 [thread overview]
Message-ID: <4464BAFA.2030103@trash.net> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25533F@xavier.staff.greatlakes.net>
Andy Furniss wrote:
> One thing to note is that HFSC will drop, rather than pass unshaped,
> traffic that is unclassified.
>
> So if you don't use a default class and don't filter arp to a class then
> HFSC will appear broken whereas HTB will work.
Good point, that is a trap that might easily make it appear as if HFSC
is stalling under some conditions.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-05-12 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 17:02 [LARTC] HFSC and prioritization Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-11 20:19 ` Jody Shumaker
2006-05-12 5:24 ` Patrick McHardy
2006-05-12 5:31 ` Patrick McHardy
2006-05-12 8:03 ` Patrick McHardy
2006-05-12 13:33 ` Andy Furniss
2006-05-12 15:30 ` Jody Shumaker
2006-05-12 16:42 ` Patrick McHardy [this message]
2006-05-12 16:56 ` Patrick McHardy
2006-05-12 17:49 ` Alexandru Dragoi
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=4464BAFA.2030103@trash.net \
--to=kaber@trash.net \
--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