All of lore.kernel.org
 help / color / mirror / Atom feed
From: <lartc@gileswestwood.co.uk>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Wondershaper updates.
Date: Mon, 31 Mar 2003 22:41:25 +0000	[thread overview]
Message-ID: <marc-lartc-104915057706867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104913989626740@msgid-missing>

I think I'll use htbinit, seems the most understandable. Seems a waste
that people with lots of experience who are very into this stuff don't
compile all the findings into a generic script(s) with parameters that
any newbie can configure and benefit from.

G.

> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl 
> [mailto:lartc-admin@mailman.ds9a.nl] On Behalf Of Martin A. Brown
> Sent: 31 March 2003 20:59
> To: lartc@gileswestwood.co.uk
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] Wondershaper updates.
> 
> 
> If you want a more general configuration interface to HTB, 
> you can use htb.init, which allows an arbitrary configuration 
> of traffic control:
> 
>   http://sourceforge.net/projects/htbinit
> 
> Or, if you prefer a more fully featured language for 
> describing traffic,
> tcng:
> 
>   http://tcng.sourceforge.net/
> 
> See my article on tcng + htb:
> 
>   http://linux-ip.net/articles/htb-and-tcng.html
> 
> If you are feeling like contributing, you could write some 
> tcng configuration files which solve your problem and publish them.
> 
> -Martin
> 
>  : Wondershaper htb seems to work fine. It would be great if 
> it had some
>  : more features. I.E if people on this mailing list could 
> contribute. I
>  : use a fantastic contributed firewall script called 
> monmotha that covers
>  : lots of the features that you might want from a firewall.
>  :
>  : I'd find it useful if wondershaper could:-
>  :
>  : 1. Specifiy hi-priority ports, most specifically port 80 
> so people can
>  : always browse on my shared connection.
>  : 2. integrate this script to allow special game priorities 
> to be setup
>  : http://mailman.ds9a.nl/pipermail/lartc/2002q3/004827.html
>  :
>  : The extra features don't have to get in the way of the 
> normal operation
>  : surely.
>  :
>  : G.
>  :
>  : ----------------------------------------------------------------
>  : Giles Westwood
>  : Web Developer
>  : Mob: 07764611148
>  : Tel:   01132781591
>  : Web: http://www.gileswestwood.co.uk
>  : ----------------------------------------------------------------
>  :
>  :
>  : _______________________________________________
>  : LARTC mailing list / LARTC@mailman.ds9a.nl
>  : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: 
http://lartc.org/
 :

-- 
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/

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

  parent reply	other threads:[~2003-03-31 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 19:43 [LARTC] Wondershaper updates lartc
2003-03-31 19:58 ` Martin A. Brown
2003-03-31 22:41 ` lartc [this message]
2003-03-31 23:40 ` Martin A. Brown

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-104915057706867@msgid-missing \
    --to=lartc@gileswestwood.co.uk \
    --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.