From: "Jonas Lindqvist" <69link@telia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] A tc htb/iptables rate control script for ADSL
Date: Wed, 17 Apr 2002 16:42:39 +0000 [thread overview]
Message-ID: <marc-lartc-101906199219360@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101900137903338@msgid-missing>
----- Original Message -----
From: "alex" <alex@bennee.com>
> # For outgoing packets we need to mark stuff
> /sbin/iptables -t mangle -A to-dsl -p tcp --dport 22 -j MARK
> --set-mark 1
>
> /sbin/iptables -t mangle -A to-dsl -p tcp --dport 80 -j MARK
> --set-mark 2
I'd also do like this:
iptables -t mangle -A to-dsl -p tcp --dport 22 -j MARK --set-mark 1
iptables -t mangle -A to-dsl -p tcp --dport 22 -j RETURN
iptables -t mangle -A to-dsl -p tcp --dport 80 -j MARK --set-mark 2
iptables -t mangle -A to-dsl -p tcp --dport 80 -j RETURN
etc...
Otherwise iptables will do the whole "to-dsl" list for every packet. In
your case ot wouldn't matter except for some extra CPU usage. But if you
would like to mark port 80 as bulk-traffic and ACK's as interactive
traffic, then those port 80 ACK's could be marked as bulk which you
wouldn't want it to.
Which brings me to another subject :) If your DSL-connection have
different bandwidth like 1mbit/128kbit then your download speed could be
destroyed by huge queues in your uplink.
I'd guess this would do the trick.
# Set ACK as prioritized traffic (ACK's are less than 100 bytes)
$IPTABLES -t mangle -A MANGLE_MARK -p tcp -m length --length :100 -j
MARK --set-mark 1
$IPTABLES -t mangle -A MANGLE_MARK -p tcp -m length --length :100 -j
RETURN
(You could probably mark ACK's with --tcp-flags SYN,FIN,RST ACK. But I
have not tested that yet.)
They also mention this here: http://lartc.org/wondershaper/
/Jonas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-04-17 16:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 23:50 [LARTC] A tc htb/iptables rate control script for ADSL alex
2002-04-17 8:34 ` Martin Devera
2002-04-17 9:07 ` Alex Bennee
2002-04-17 9:33 ` Martin Devera
2002-04-17 12:46 ` Stef Coene
2002-04-17 12:54 ` Martin Devera
2002-04-17 13:10 ` Stef Coene
2002-04-17 13:43 ` Alex Bennee
2002-04-17 13:46 ` Martin Devera
2002-04-17 13:50 ` Stef Coene
2002-04-17 15:57 ` Don Cohen
2002-04-17 16:03 ` Martin Devera
2002-04-17 16:09 ` Martin Devera
2002-04-17 16:42 ` Jonas Lindqvist [this message]
2002-04-17 21:25 ` Nils Lichtenfeld
2002-04-17 21:27 ` Martin Devera
2002-04-17 21:30 ` Nils Lichtenfeld
2002-04-17 21:48 ` Nils Lichtenfeld
2002-04-19 8:32 ` Martin Devera
2002-04-26 13:31 ` Nils Lichtenfeld
2002-04-26 14:43 ` Martin Devera
2002-04-27 16:05 ` Nils Lichtenfeld
2002-04-27 16:06 ` 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-101906199219360@msgid-missing \
--to=69link@telia.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.