All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oki DZ okidz@telkom.net
To: lartc@vger.kernel.org
Subject: [LARTC] Limiting bandwidth according to certain protocols
Date: Wed, 17 Jan 2001 04:22:37 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416892@msgid-missing> (raw)

<PRE>Hi,

I'd like to create some bandwidth limiters on a server with the 
following typical configuration.

Server
/------------------\
128Kbps  |                  | 10Mbps
[Internet]----------|-[eth1]----[eth0]-|----------[Internal LAN]
|<i> [Squid]          |
</I>\------------------/


I have Squid running on the server.
I'd like to provide a higher priority for users that use POP servers 
somewhere on the Internet than those who use the web proxy; I mean, 
anyone that connects to port 110 on some servers on the internet will 
have higher priority compared to those who use port 80 (my Squid 
connects to its parent on port 80). So that anyone could be retrieving 
their emails faster when the line is currently busy serving the web 
users' requests.

As I understand it, you can limit the bandwith for outgoing traffic; so 
on the example above, limits apply for eth1--&gt;Internet and 
eth0--&gt;Internal LAN. My question is: how do you limit the bandwidth for 
the return packets (i.e.: the responses of the packets that once were 
requested by the web users).

So, what I'd like to do is to let the (proxied) web users to use the 
available outgoing bandwidth for the requests, but when the response 
packets return, those packets should be delivered according to some 
limits and should have lower priority compared to the returning POP 
packets.

How can I accomplish this using ipchains, ip, and tc?
BTW, explanations would be sufficient; I will look up the man pages for 
implementing the explanations using those commands.

Thanks in advance,
Oki



</PRE>

                 reply	other threads:[~2001-01-17  4:22 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-98373940416892@msgid-missing \
    --to=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.