Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Default Class
Date: Tue, 18 Nov 2003 18:35:20 +0000	[thread overview]
Message-ID: <marc-lartc-106918085901732@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106911155331153@msgid-missing>

On Tuesday 18 November 2003 00:23, Chijioke Kalu wrote:
> Hi all,
>
> In my script, i assigned specific ip's to set classes, and assume by
> default any other ip not matching my list of ips falls into the default
> class. Consequently ave had occasions whenever systems that have ip's which
> am sure fall into the default class,  are in use, traffic tends to get
> congested on "normal" classes...
I suppose you use htb ....

> NB. my default class has the lowest priority
>
> 1. Is this meant to be so, if not how can i correct it?
It's not meant to be like that.

> 2. Is it possible to know the sort of traffic passing thru the default
> class?  If possible improve the rate of other classes by matching important
> traffic back to a higher priority class.
No.  Default class is used after all other filters are checked.

> 3. Can I also match by mac-addresses?
Yes : iptables + fw filter.

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/

  reply	other threads:[~2003-11-18 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 23:23 [LARTC] Default Class Chijioke Kalu
2003-11-18 18:35 ` Stef Coene [this message]
2003-11-18 19:47 ` Chijioke Kalu

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-106918085901732@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox