From: Julien Vehent <julien@linuxwall.info>
To: "Mihamina Rakotomandimby (R12y)" <mihamina@lab.vectoris.fr>
Cc: netfilter@vger.kernel.org
Subject: Re: traffic shaping documentation
Date: Tue, 21 Apr 2009 13:18:12 +0200 [thread overview]
Message-ID: <154d9336a3c358635883b5c3972a149b@localhost> (raw)
In-Reply-To: <49ED88BD.4070406@lab.vectoris.fr>
Hello,
By your signature, I suppose you read french. Then, maybe you will find
some useful information in the doc I wrote a few months ago :
http://wiki.linuxwall.info/doku.php?id=ressources:dossiers:advanced_networking:2_qos_traffic_control
Hope it helps...
Julien
On Tue, 21 Apr 2009 11:50:05 +0300, "Mihamina Rakotomandimby (R12y)"
<mihamina@lab.vectoris.fr> wrote:
> Hi all,
> I have a gateway on which I would like to implement traffic shapping
based
> only on ports.
> The simple schema:
>
> 15-PCs-LAN <-> (eth0)[Gateway](eth1) <-> Internet
>
> The gateway is also my workstation and it holds many services accessibles
> from the LAN and from Internet.
>
> The problem is HTTP traffic is so much that SSH connection to the remote
> servers I manage are slow.
>
> Therefore, I would like to give:
> - highest priority to SSH (INPUT/OUTPUT/FORWARD dport 22)
> - normal priority to others (INPUT/OUTPUT/FORWARD dport:FTP, SVN,...)
> - lowest priority to HTTP
> (dport 80 REDIRECTed INPUT on squid's 3128, OUTPUT dport 80)
>
> The perfect would be to shape it on the OUTPUT chain, because I would
like
> also the shape affects my (Gateway) behaviour.
>
> I am not asking for the direct solution, I am first asking if what I
want:
> - is a good idea
> - implementable
> - is documented in another place than lartc.org
> (which is good but too much big for my simple needs)
>
> Thank you for any tips.
--
julien
http://jve.linuxwall.info/blog
next prev parent reply other threads:[~2009-04-21 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 8:50 traffic shaping documentation Mihamina Rakotomandimby (R12y)
2009-04-21 11:18 ` Julien Vehent [this message]
2009-04-21 13:26 ` SISINT BA
2009-04-21 14:09 ` Julien Vehent
2009-04-21 14:23 ` SISINT BA
2009-04-21 15:23 ` Julien Vehent
2009-04-21 11:29 ` Michele Petrazzo - Unipex
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=154d9336a3c358635883b5c3972a149b@localhost \
--to=julien@linuxwall.info \
--cc=mihamina@lab.vectoris.fr \
--cc=netfilter@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