From: ronald.phannee@planet.nl
To: lartc@vger.kernel.org
Subject: Re: [LARTC] prioritizing INCOMING traffic
Date: Sun, 20 Jan 2002 15:31:36 +0000 [thread overview]
Message-ID: <marc-lartc-101154074330334@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101153942328316@msgid-missing>
On Sun, 20 Jan 2002, Martin Devera wrote:
Hi Martin
> > iptables -t mangle -A PREROUTING -i ppp0 -p tcp --sport ssh -j TOS --set-tos Minimize-Delay
> > iptables -t mangle -A OUTPUT -o ppp0 -p tcp --dport ssh -j TOS --set-tos Minimize-Delay
>
> but this itself will not priorize anything .. depends on routers outside
I know so that is why I do use:
tc qdisc add dev ppp0 root handle 1: prio
# traffic put by kernel in band 0 based on TOS bit just set by iptables
tc qdisc add dev ppp0 parent 1:1 handle 10: sfq
# traffic put by kernel in band 1 based on TOS bit just set by iptable
tc qdisc add dev ppp0 parent 1:2 handle 20: tbf rate 61kbit latency 50ms burst 1540
# traffic put by kernel in band 2 based on TOS bit just set by iptable
tc qdisc add dev ppp0 parent 1:3 handle 30: sfq
This DOES shape my traffic , or am I wrong?
> > Now my question is if the opposite rules do make sense also?
> > iptables -t mangle -A PREROUTING -i ppp0 -p tcp --dport ssh -j TOS --set-tos Minimize-Delay
> > iptables -t mangle -A OUTPUT -o ppp0 -p tcp --sport ssh -j TOS --set-tos Minimize-Delay
> > My intention is to give priority to incoming (from internet to my linux
> > box) ssh sessions also.
>
> It is nonsence .. Once packet is in your box all QoS decisions was already
> made.
Ok I agree :) But my thinking was that I CAN influence the return traffic
thus slowing down (tcp window mechanism) the BULK connections and not
slowing down the interactive traffic.. Makes sense or totally not? :P
Best regards,
--
Ronald Verlaan
http://80.60.86.86
ronald.phannee@planet.nl
--------------------------------------------------------------------------
Mickey Mouse wears a Spiro Agnew watch.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-20 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 15:09 [LARTC] prioritizing INCOMING traffic ronald.phannee
2002-01-20 15:15 ` Martin Devera
2002-01-20 15:31 ` ronald.phannee [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=marc-lartc-101154074330334@msgid-missing \
--to=ronald.phannee@planet.nl \
--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