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
Kilian Krause
2002-Mar-14 18:25 UTC
Re: How can I prioritize incoming interactive traffic?
Hi Torgil, sorry, i''m not that far in traffic conditioning, that i can answer your first question, but here''s my answer to the second: S> Question 2: S> 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. S> you might try with the limit.conn-script from http://www.chronox.de/ to slow down individuals.. as far as they connect from static ips everything is fine.. if you want some interactive limiter i bet you''re better off with a classful conditioning.. -- Best regards, Kilian mailto:kk@verfaction.de ---------------------------------------------------------------- /dev/random reads at Thursday, March 14, 2002 19:22: There''s my way, and then there''s the easy way. ----------------------------------------------------------------
Thank you for your reply! The scripts on the site really gave me inspiration. As for my second question I think I will dynamically add/delete filtering rules on connection/disconnection of players on our game-server. I think I''ll use u32 instead of fw filtering though. But my first question remains unresolved (bw-limit non-interactive incoming traffic to reduce latency on more important traffic). What I''m thinking about is a thread which measures bandwith on interactive traffic and then use "tc filter change" on the bandwith limiting rule. Has anyone done this before or have a more clever solution? /Torgil ----- Original Message ----- From: "Kilian Krause" <kk@verfaction.de> To: <lartc@mailman.ds9a.nl> Cc: <zob_soulfly@hotmail.com> Sent: Thursday, March 14, 2002 7:25 PM Subject: Re: [LARTC] How can I prioritize incoming interactive traffic?> Hi Torgil, > > sorry, i''m not that far in traffic conditioning, that i can answer your > first question, but here''s my answer to the second: > > S> Question 2: > S> 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. S> > > you might try with the limit.conn-script from http://www.chronox.de/ to > slow down individuals.. as far as they connect from static ips > everything is fine.. if you want some interactive limiter i bet you''re > better off with a classful conditioning.. > > > -- > Best regards, > Kilian mailto:kk@verfaction.de > ---------------------------------------------------------------- > /dev/random reads at Thursday, March 14, 2002 19:22: > There''s my way, and then there''s the easy way. > ---------------------------------------------------------------- > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ >