Author Topic: Fighting over bandwidth.  (Read 4890 times)

DKG

  • Posts: 64
  • Turrets: +0/-2
Fighting over bandwidth.
« on: September 20, 2006, 08:38:13 pm »
I've recently discovered tremulous, an amazing game.
I also share a 2mb connection with 3 people:(

As a noob, having just got a goon, I was very pleased with myself :oops:
So off I went, about the same time my cousin decided to fire up bearshare/limewire or some equally bandwidth-hungry p2p client.

What happened?  I was faced with my first human, only to freeze and have the sh!t machine-gunned out of me.

As you can imagine (if you remember back in the day as a noob) this was VERY frustrating.

I now arrive at my question.
Without completely blocking kazza/limewire..... is there anyway of playing about with my router's QoS settings to my advantage (whilst Tremming)?

Bearing in mind-
1> my cousin is alot bigger than me (no "kindly" requesting he get his porn from the local videoclub)
2> he pays a 3rd of the bill (no disconnecting his cable from the router)

next_ghost

  • Posts: 892
  • Turrets: +3/-6
Fighting over bandwidth.
« Reply #1 on: September 20, 2006, 09:13:15 pm »
That depends on the type and firmware of your router.
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.

Stof

  • Posts: 1343
  • Turrets: +1/-1
Fighting over bandwidth.
« Reply #2 on: September 20, 2006, 09:14:40 pm »
He pays one third he gets one third. He'll have to limit his upload rate while others are using the connection there is no other way. Well, you could always install some Linux computer as a new router and configure some QoS to put p2p packets on the lowest priority but it takes quite some work to setup correctly.
urphy's rules of combat
8 ) Teamwork is essential; it gives the enemy someone else to shoot at.
18 ) Make it too tough for the enemy to get in and you can't get out.

[db@]Megabite

  • Posts: 613
  • Turrets: +3/-0
    • http://www.tremulous.info
Re: Fighting over bandwidth.
« Reply #3 on: September 20, 2006, 09:17:35 pm »
Quote from: "DKG"

Without completely blocking kazza/limewire..... is there anyway of playing about with my router's QoS settings to my advantage (whilst Tremming)?


There should be a way... ;)
Mind that there are two basically different ways QoS may work. First and easiest option should be giving traffic priority by IP.
Just give your PC a fixed IP and configure the router to give your IP the highest priority. Tremulous is not sucking much bandwidth and filesharing stuff usually does not cry when it is throtteled a bit for a while... ;)

The second way QoS may work is by application / port. You can assign priorities to certain kinds of traffic. As most games use UDP instead of TCP you may be able to generally put UDP in favor. Otherwise you may have to look at ports and lower priority for ports used by filesharing progs, HTTP (TCP 80) and FTP (TCP 21).

Mind that only one or both ways may be supported by your router. Most routers don't support QoS. I use the IP priority solution at home. My wife does not need more than half an mbit for surfing... ;)

Danny
url=http://www.tremulous.info][/url]


DKG

  • Posts: 64
  • Turrets: +0/-2
Fighting over bandwidth.
« Reply #4 on: September 20, 2006, 09:22:52 pm »
Paradox:
Setting up a Linux box as a router will give me more Trem-time.
(setting up a Linux router with QoS settings in my favour will consume HOURS of Trem-time)

I think, as is, the glass is half full. Tremulous at non porn time is better than no Tremulous.

janev

  • Spam Killer
  • *
  • Posts: 534
  • Turrets: +130/-26
Fighting over bandwidth.
« Reply #5 on: September 20, 2006, 09:24:49 pm »
well if you get along ok ask him to install a netlimiting program to limit the bandwidth he uses while others are online. for example http://www.netlimiter.com/
this is what i used when sharing a connection with a p2p junkie.

I could also suggest martial arts training but i doubt that will help in the immediate future.
Author of "The quick beginner's guide to playing tremulous"
Founding member of the "undefeated in clanwars since 2006" club and narcissist extraordinaire.


"Your quote-tower trolling reminds me of two dogs fighting over a piece of poo." [c] Ingar

DKG

  • Posts: 64
  • Turrets: +0/-2
Fighting over bandwidth.
« Reply #6 on: September 20, 2006, 09:30:44 pm »
[db@]Megabite,  My router supports port QoS, I'll give it a try.
I know the ports most p2p programs use, to lower their priority, what ports does Trem use? (TCP/UDP)


janev, Martial arts training would take far too long.  I'm Trem-hungry NOW!

David

  • Spam Killer
  • *
  • Posts: 3543
  • Turrets: +249/-273
Fighting over bandwidth.
« Reply #7 on: September 20, 2006, 11:35:59 pm »
I have a router running OpenWRT, it is basically a Linux box :)
I can have bit torrent etc running and trem doesn't notice :)

if you have a linksys WRT54G you should check it out. open source router :)
Any maps not in the MG repo?  Email me or come to irc.freenode.net/#mg.
--
My words are mine and mine alone.  I can't speak for anyone else, and there is no one who can speak for me.  If I ever make a post that gives the opinions or positions of other users or groups, then they will be clearly labeled as such.
I'm disappointed that people's past actions have forced me to state what should be obvious.
I am not a dev.  Nothing I say counts for anything.

Undeference

  • Tremulous Developers
  • *
  • Posts: 1254
  • Turrets: +122/-45
Fighting over bandwidth.
« Reply #8 on: September 20, 2006, 11:47:10 pm »
The default Tremulous port is UDP 30720.
Need help? Ask intelligently. Please share solutions you find.

Thats what we need, helpful players, not more powerful admins.

DKG

  • Posts: 64
  • Turrets: +0/-2
Fighting over bandwidth.
« Reply #9 on: September 20, 2006, 11:52:25 pm »
Linksys WAG354G. Untill a reasonable mothod of sharing bandwidth is found I'm stuck with "sly" solutions (removing UTP, restarting router with different IP without DHCP...)

Paradox

  • Posts: 2612
  • Turrets: +253/-250
    • Paradox Designs
Fighting over bandwidth.
« Reply #10 on: September 21, 2006, 12:34:31 am »
Limit the router to his 1/3, or get a better job and buy your own t1 line

∧OMG ENTROPY∧

Basilisco

  • Posts: 592
  • Turrets: +24/-5
    • http://wilhelmrahn.googlepages.com/
Fighting over bandwidth.
« Reply #11 on: September 21, 2006, 02:40:36 am »
One short AND long term solution, crash his hd.

If the HD of somene that is a compulsive downloader crashes, he will lose the will to download anything else in fear that it will happend again.
This behaviour will last some months before he feels it's "safe" to start downloading again, in which case you'll have to take his confidence away by repeating the process :D

I can confirm this after losing gigs and gigs of precious info AND porn/anime/warez/moviez. Sad sad story..

Taiyo.uk

  • Posts: 2309
  • Turrets: +222/-191
    • Haos Redro
Fighting over bandwidth.
« Reply #12 on: September 21, 2006, 06:16:12 am »
m0n0wall ftw!

I set up an old box with m0n0wall (FreeBSD based firewall with traffic shaping) and configured the shaper to give trem enough bandwidth with good results. Installation is as easy as killing dretches with a lucifer cannon as you just download a bootable image that you burn to a CF card or hard drive.

To configure the traffic shaper I used the auto shaper (de-prioritises P2P traffic, etc.) then added rules specific to trem.

http://m0n0.ch/wall/

HTH

next_ghost

  • Posts: 892
  • Turrets: +3/-6
Fighting over bandwidth.
« Reply #13 on: September 21, 2006, 08:12:05 am »
Quote from: "DKG"
[db@]Megabite,  My router supports port QoS, I'll give it a try.
I know the ports most p2p programs use, to lower their priority, what ports does Trem use? (TCP/UDP)


Then set your IP:30720 UDP (source) to the highest priority. If there're some advanced settings, try to find something like minimize delay.
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.