All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] interface making
Date: Mon, 01 Dec 2003 07:33:39 +0000	[thread overview]
Message-ID: <marc-lartc-107026408704052@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106904321519462@msgid-missing>

Hello Cheongseng,

 : before this, when we want to setup the gateway to provide QoS. we need
 : to go though LARTC, follow the step configuration. finally, we need to
 : write the config. file using bash. then we execute the file to complete
 : the setting, m i rite?

The process is very much like this, although the exact procedure depends
on the nature of the tools you are using.

 : i suggest to make this complex steps more easier. how i make it?? i m
 : trying to make a form using JAVA, that form is for the adminstritor to
 : control the traffic. for example,
 :
 : at the beginning the adminstritor set the http higher priority. after
 : some times, he want to make charging. the adminstritor must have some
 : knowledge about the LARTC only he able to make the charging. because he
 : must charge the value in the config. file and execute it again.

To my knowledge, this is true now, and to a certain extent cannot be
otherwise.  Here's what I mean.  Each traffic control structure created in
the kernel is static, and would require changing a configuration file or
setting.

To minimize the administrative hassle of running a traffic control device,
you could use the tcng language [0].  This provides a much more
approachable way to discuss and manage traffic control systems.  The tcng
distribution comes with some good example configuration files, but you can
also consult a HOWTO I have written [1].

 : if we make a form to replace all this jobs. when we make changes in the
 : form, then the value in the config.file will be change follow the value
 : inside the form.

It sounds to me as though you wish to have a form front end (D/HTML) which
allows an admin to configure the traffic control system on the fly.  There
would doubtless be quite a niche market for this sort of an interface on
the traffic control system.  I certainly wouldn't want to tackle this job.

 : the adminstritor can make the charges by using the form. then the QoS
 : will become more user friendly, am i rite??

QoS is not a particularly user friendly topic, though, because of the
complexity of the systems involved.  Not only does the administrator need
to understand how burstiness and latency can be affected by different QoS
mechanisms, but this same person needs to understand a great deal about
the contents of IP packets.

I'd suggest examining tcng to see if it meets your needs for sufficiently
demystifying traffic control under Linux.  Good luck!

-Martin

 [0] http://tcng.sourceforge.net/
 [1] http://tldp.org/HOWTO/Traffic-Control-tcng-HTB-HOWTO/

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-12-01  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  4:24 [LARTC] interface making wong cheongseng
2003-11-17 19:26 ` Stef Coene
2003-11-18  8:53 ` wong cheongseng
2003-12-01  7:33 ` Martin A. Brown [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-107026408704052@msgid-missing \
    --to=mabrown-lartc@securepipe.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.