From: Wolfgang Meyerle <procrash@neusob.de>
To: netfilter@lists.netfilter.org
Subject: Qos Problem
Date: Sun, 13 Feb 2005 20:55:25 +0100 [thread overview]
Message-ID: <420FB0AD.9050008@neusob.de> (raw)
Hi, has anybody of you ever tried Qos with iptables?
===============================
My Problem is that when I set up htb to classify my packets every
traffic should go to one of three classes.
-The first class is the priorisized one (thought for myself to put in
http packets)
-the second one is for peer2peer traffic which should be unpriorisized.
-And third is for the rest of the packets.
Now classifying works very good, but when I want to surf the www the htb
qdisc doesn't seem to give my http packets fast sending.
My Browser reacts ver slow and surfing seems quite impossible.
I thought the problem could be in the pfifo fast queues that the every
leaf is assigned by htb.
For this I introduced and bfifo with limit for every leaf.
I gave it simply a limit of 1500bytes no exactly knowing what I'm doing.
Now I can browse perfectly but the throughput of my peer2peer program is
slow as hell.
To differentiate the Peer2Peer Traffic I uses ipp2p filter with iptables.
What's wrong in my thoughts? Can anybody of you tell me?
Cheers
Wolfgang Meyerle
reply other threads:[~2005-02-13 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=420FB0AD.9050008@neusob.de \
--to=procrash@neusob.de \
--cc=netfilter@lists.netfilter.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