All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Sibon sibon@triple-it.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Basic shaping works!
Date: Thu, 19 Oct 2000 09:17:50 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216814@msgid-missing> (raw)

<PRE>Hi all,

Yesterday I got the tip about depmod -a but that didn't work: lots of
undefined symbols and other stuff. I decided to code the entire QOS stuff
directly in the kernel and now it works!

I had some problems with the example of the iproute-2.4 page but that was
because I mixed the 'prio' in the tc filter statement. I found out that when
the high prio belongs to the 'low-bandwidth' class, this doesn't seem to
work.

I then started deleting parts of the configuration and somewhere down the
line it worked! After I changed the prio-order in the tc filter statement
things worked like I expected they should work.

As soon as I get some time, I hope to go on with the examples in combination
with the firewall-rules to give higher priority to ssh traffic and so on.

By the way, are there people here who have also played with the ingres
policer qdisc?

And what tools do you use to monitor the network-load? I am currently
running XCounter 1.0.3 but in my research on the web about traffic-shaping I
have seen some very impressive graphs with the different QOS'ses (but I
believe that was for FreeBSD). I would already be pleased with a tool that
displays a graph over a period of time (like Perfmon in Windows NT).

Thanks again for your time,

Clemens Sibon



</PRE>

                 reply	other threads:[~2000-10-19  9:17 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-98373938216814@msgid-missing \
    --to=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.