From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Confuse, putting packets in wrong mangle table.
Date: Sat, 05 Feb 2005 12:30:40 +0000 [thread overview]
Message-ID: <4204BC70.5030005@dsl.pipex.com> (raw)
In-Reply-To: <200501191657.15767.rio@martin.mu>
Rio Martin. wrote:
> On Monday 31 January 2005 23:17, Andy Furniss wrote:
>
>>Ahh - I thought that squid could limit connections based on the rate the
>>client could sustain.
>>You can shape incoming to squid with imq if hooked after nat, because
>>its traffic will have real dst address - other will have been denatted.
>
>
> Could you give me some example, how to do that?
> Thanks ..
>
There may be a way to do this with a dummy device soon, but for now you
need too patch kernel with imq from http://www.linuximq.net choose to
hook after nat (may be default - the first letter in imq kernel config
needs to be A)
Set up htb with your rules for sharing/ priorotising interactive traffic
attached to imq0.
In prerouting mangle you can do some marking eg. small tcp/udp to get
priority. Then append a rule like this -
iptables -t mangle -A PREROUTING -i eth0 -j IMQ --todev 0
Somewhere in you htb setup make a class for you squid traffic and filter
traffic to it something like -
tc class add dev imq0 parent 1:2 classid 1:33 htb rate 220kbit ceil
480kbit quantum 1500 prio 1
tc filter add dev imq0 protocol ip parent 1:0 prio 1 u32 \
match ip dst 220.1.1.1 flowid 1:33
You also need to first modprobe imq if it's a module and bring it up with -
modprobe imq numdevs=1
ip link set imq0 up
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-02-05 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 10:05 [LARTC] Re: Confuse, putting packets in wrong mangle table Rio Martin.
2005-01-25 12:41 ` Andy Furniss
2005-01-26 11:08 ` Rio Martin.
2005-01-27 12:37 ` Andy Furniss
2005-01-28 6:48 ` Rio Martin.
2005-01-29 0:55 ` Andy Furniss
2005-01-29 11:30 ` Rio Martin.
2005-01-31 23:17 ` Andy Furniss
2005-02-01 5:41 ` Rio Martin.
2005-02-05 12:30 ` 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=4204BC70.5030005@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 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.