From: Leszek Olszewski <rewt@post.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] I seem to have a problem with HTB
Date: Thu, 13 Dec 2001 09:01:10 +0000 [thread overview]
Message-ID: <marc-lartc-100823414120710@msgid-missing> (raw)
Hello,
I have compiled HTB into kernel 2.4.16 and set up simple traffic shaping
just to figure how it works. My init script looks as follows:
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 1: htb default 30
tceth0="tc class add dev eth1"
$tceth0 parent 1: classid 1:1 htb rate 128kbit burst 2k
$tceth0 parent 1:1 classid 1:10 htb rate 128kbit burst 2k
$tceth0 parent 1:1 classid 1:20 htb rate 64kbit ceil 96kbit burst 2k
$tceth0 parent 1:1 classid 1:30 htb rate 1kbit ceil 96kbit burst 2k
tcqdisc="tc qdisc add dev"
$tcqdisc eth1 parent 1:10 handle 10: sfq perturb 10
$tcqdisc eth1 parent 1:20 handle 20: sfq perturb 10
$tcqdisc eth1 parent 1:30 handle 30: sfq perturb 10
u32="tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32"
$u32 match ip protocol 1 0xff flowid 1:10
$u32 match ip sport 22 0xffff flowid 1:10
$u32 match ip sport 119 0xffff flowid 1:10
$u32 match ip sport 80 0xffff flowid 1:20
$u32 match ip sport 110 0xffff flowid 1:20
- Pretty much the example script from Advanced Routing HowTo. I have
Internet on eth0 and LAN via NAT on eth1.
The problem is that after appx. 6 hours or so the local network starts
behaving strange - either it doesn't work at all or just packets from
certain classes don't go through the NAT and get dropped. In syslog I have
found following entries:
Dec 13 09:33:25 mail kernel: HTB delay 224640 > 5sec
Dec 13 09:33:27 mail kernel: HTB delay 224474 > 5sec
Dec 13 09:33:29 mail kernel: HTB delay 224272 > 5sec
Dec 13 09:33:32 mail kernel: HTB delay 223977 > 5sec
Dec 13 09:33:32 mail kernel: HTB delay 223973 > 5sec
Dec 13 09:33:37 mail kernel: HTB delay 223473 > 5sec
Dec 13 09:33:38 mail kernel: HTB delay 223377 > 5sec
Dec 13 09:33:38 mail kernel: HTB delay 223373 > 5sec
There is many more of them, they start to appear just at the time when the
network starts dying.
Any ideas what is wrong pretty please ;) ??
Regards,
Leszek
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2001-12-13 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 9:01 Leszek Olszewski [this message]
2001-12-13 9:49 ` [LARTC] I seem to have a problem with HTB bert hubert
2001-12-14 16:15 ` Stefan Rompf
2001-12-14 16:20 ` Leszek Olszewski
2001-12-14 17:24 ` Patrik
2001-12-15 13:52 ` bert hubert
2001-12-17 6:39 ` 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-100823414120710@msgid-missing \
--to=rewt@post.pl \
--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.