From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: [LARTC] shaping packets in PREROUTING - is it legal?
Date: Fri, 31 Jan 2003 15:55:58 +0000 [thread overview]
Message-ID: <marc-lartc-104402866815078@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Hi!
I've got a box which redirects http traffic to another box (proxy). I'd like
to do some traffic shaping on this box as well (including traffic destined
for the proxy). In order to do that I need to intercept packets in the
mangle table in PREROUTING, shape it and then it will be redirected when it
gets to the nat table in PREROUTING (or not, if it is not http).
So now I have
| eth0 (incoming)
.---------.
| QoS box |
`---------'
| eth1 (outgoing)
and I have
iptables -t mangle -N qos
iptables -t mangle -A PREROUTING -j qos
iptables -t nat -A PREROUTING -i eth1 -s .... -p tcp --dport 80 -j DNAT --to ...
and then a couple of rules in the qos table which sets skb->priority so that
tc can delay the packets (I'm using HTB)
Problem is that if I do this, the box stops routing traffic until I remove
the qos filters _and_ the tc queuing discplines.
Any ideas what is happening here, why it doesn't work and what I should do
different?
--
Regards
Abraham
Time is fluid ... like a river with currents, eddies, backwash.
-- Spock, "The City on the Edge of Forever", stardate 3134.0
___________________________________________________
Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
P.O. Box 3472, Matieland, Stellenbosch, 7602
Cell: +27 82 565 4451 Http: http://www.frogfoot.net/
Email: abz@frogfoot.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2003-01-31 15: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=marc-lartc-104402866815078@msgid-missing \
--to=abz@frogfoot.net \
--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