From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB stalling
Date: Fri, 22 Apr 2005 14:01:03 +0000 [thread overview]
Message-ID: <4269039F.93FD068A@iswest.com> (raw)
In-Reply-To: <258b6f705041723197f494890@mail.gmail.com>
> hareram wrote:
>
> Hi all
>
> iam also facing the same problem what Mr Antoni have
> even i have done many kind of experment, but i could not resolve is
> this bug in FC3,
> but when i does the FC1 its working fine
>
> I found difference from FC1 to FC3 is
>
> FC1 iptables 1.2.8 HTB 3.12
> FC3 iptable 1.2.11 htb 3.16
>
> can some experts coment on this
> hare
Although this stalling issue may still be a timer problem rather than
HTB, there are bugs in versions of HTB < 3.17 so you MUST patch the
kernel so HTB is at least 3.17. I don't know about iptables.
Do remember that FC3 contains much BETA; you really should be using
something less "bleeding edge" for a server.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-04-22 14:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 6:19 [LARTC] HTB stalling Krystian Antoni
2005-04-18 10:56 ` Kunszt Arpad
2005-04-19 21:58 ` Andy Furniss
2005-04-20 6:13 ` Krystian Antoni
2005-04-21 23:49 ` Andy Furniss
2005-04-22 5:21 ` hareram
2005-04-22 12:24 ` Kunszt Arpad
2005-04-22 14:01 ` gypsy [this message]
2005-04-22 20:18 ` Krystian Antoni
2005-04-22 20:29 ` Krystian Antoni
2005-04-23 1:48 ` gypsy
2005-04-23 7:14 ` Krystian Antoni
2005-04-24 20:42 ` Andy Furniss
2005-04-24 20:51 ` Andy Furniss
2005-04-24 21:13 ` Kunszt Arpad
2005-04-24 21:24 ` Patrick McHardy
2005-04-25 4:00 ` Krystian Antoni
2005-04-25 4:06 ` Krystian Antoni
2005-04-25 7:04 ` Kunszt Arpad
2005-04-25 9:51 ` Andy Furniss
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=4269039F.93FD068A@iswest.com \
--to=gypsy@iswest.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.