From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ingress QoS
Date: Wed, 17 Mar 2004 09:52:00 +0000 [thread overview]
Message-ID: <40581FC0.5040408@dsl.pipex.com> (raw)
In-Reply-To: <20040315122000.GA28318@fpsvr1z150.dartsd66.local>
Robert Felber wrote:
> Hello guys,
>
> Setup: iptables 1.2.9 (patch-o-matic not used)
> linux 2.4.25 (gentoo vanilla, everything needed compiled in)
> eth1 -> pppoe (ppp0)
> eth0
>
> Goal: Fair queuing of incomming traffic
>
> Story:
>
> since I've failed to use IMQ with iptables 1.2.9 and linux 2.4.25,
What failed - my 2.4.24 setup may work I'll try 25 soon.
> I've tried to attach a HTB qdisc to eth0 with a root of 100mbit
> and classes with rates of 100mbit and DSL downlink speed (768 kbit).
> The downlink class I divided into important traffic (700 kbit) and
> bulk (68 kbit) - both got HTB qdiscs.
You need to set limits to 80% or less - depending on number of tcps and
how much you care about latency.
> The router packets with source 10.0.0.1 end up in the 100mbit queue, but
> I have to set this rule to prio 1 otherwise the bulk rule (src 0.0.0.0/0)
> will take place.
>
> Everything is working fine so far.
>
> Since I wanted to speed up browsing while having other downloads,
> packets with sport 80 are queued in the important queue.
> Also I wanted to be very smart and use a transparent squid.
> But then I thought twice and realized, that packets with sport 80 end up
> in squid (except it was a direct connection), thus the packets are queued
> different.
>
> Question is now: do I also have to add qdiscs to device lo, or how can I
> queue the router's incomming traffic for routers's local processes.
> If I have to add qdiscs for lo, what would be the bandwidth?
> And, would that be clever in general?
If what you want to do is controll/share incoming DSL bandwidth for
local and forwarded traffic you need to put IMQ on ppp0. I guess you
don't need to throttle/priorotise squid to the LAN for stuff that's
cached, but do when it's getting stuff from the net.
Andy.
>
> If someone is interessted in the script, drop a note.
>
> Thanks in advance,
> Rob
>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-03-17 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 12:20 [LARTC] ingress QoS Robert Felber
2004-03-17 9:52 ` Andy Furniss [this message]
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=40581FC0.5040408@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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