Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Playawireless" <tech@playawireless.com>
To: lartc@vger.kernel.org
Subject: [LARTC] switch to hb3 in production enviroment
Date: Sun, 19 May 2002 21:18:07 +0000	[thread overview]
Message-ID: <marc-lartc-102184305000723@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Hello everyone,

I am following the list since some month and thanks to all the precious indication and to the manuals I went to the following setup:

2Mbit internet---Cisco router
                                |
                            Switch--trasparent proxy server
                                |
           bridge/firewallinh/htb2+sqf linux box
                                |
                            switch--- wireless and dialup clients
                                |
                    network servers

the linux box uses redhat 7.2 with 2.4.18 kernel patched with htb 2 + bridge firewalling, i have 60 htb classes (from 64 to 512  kbit)each with sqf leaf and I am using U32 filter to select source, destination or port.I also have some firewalling iptables rules. I tested the setup for 15 days and then put it in production enviroment since it was very urgent for me. I am very happy with the erformance and it seems to be rock solid. I read something about htb3 and the new aproachso I was thinking to swithch to htb3.
Daes somebody have some results about htb3 stability in production?
In what shall I expect improvement? Somebody out there did the same thing?

Thanks in advance to all the list... I've learned a lot from it :-D

Alfredo Giordano


[-- Attachment #2: Type: text/html, Size: 3300 bytes --]

             reply	other threads:[~2002-05-19 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 21:18 Playawireless [this message]
2002-05-22 20:27 ` [LARTC] switch to hb3 in production enviroment Martin Devera

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-102184305000723@msgid-missing \
    --to=tech@playawireless.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox