All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Soulfly" <zob_soulfly@hotmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] How can I prioritize incoming interactive traffic?
Date: Thu, 14 Mar 2002 18:14:11 +0000	[thread overview]
Message-ID: <marc-lartc-101612969227836@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

Hi,

We have a ADSL connection (2Mb down, 0.7Mb up) on which we run a public Counter-Strike gaming server with lots of interactive traffic. Behind the router (Linux 2.4.17with preemptive and HTB patches) we have one member plus ftp,SMTP,HTTP servers.

Our problem is that we don't want for instance the ftp-server or downloads behind the firewall interfere with the latency of the public gaming server. I have currently solved this with a simple filters on ingress which rate-limit all traffic except our interactive traffic. However since there are people "behind" the router they don't want to have rate-limited downloads when there are no or few players connected on the game-server. Uplink traffic is not a problem with current routing tools.

Question 1:
What I want is a ingress bandwith-limiting-filter with an adaptive ratelimit which depends on current needs of the game server. Is this possible to do with current user-tools/kernel ?

Question 2:
Is there a way (without much additional code on kernel/userspace programs) to bandwidth-limit single connections on the game-server? Some people with good connections seems to flood the server with updates.

/Torgil


[-- Attachment #2: Type: text/html, Size: 2149 bytes --]

             reply	other threads:[~2002-03-14 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 18:14 Soulfly [this message]
2002-03-14 18:25 ` [LARTC] How can I prioritize incoming interactive traffic? Kilian Krause
2002-03-14 23:39 ` Soulfly

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-101612969227836@msgid-missing \
    --to=zob_soulfly@hotmail.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.