Forums | MacLife

The official client only allows you to cap uploads not downloads.

What the cap refers to in this is the top speed the data is sent, not the total amount of data being sent. You can still upload about a kazillion terabytes of data with a low cap it'll just take a lot longer. An upload cap of 40 KBps will allow me to share the same amount of total data as a cap of 20 KBps but will take me half the time to do it. If request won fit in this second's upload queue it will be scheduled for the next second's queue. Of course this assumes the application combines the request packets with the shared torrents' assigned transfer bandwidth. (If I remember correctly the data requests are handled separately.)

An upload cap does make a lot more sense than a download cap. I have to agree with the others that being able to set caps on both makes a lot of sense though. Especially for those who have significant limits on both upstream and downstream traffic.

or people that like to play online games while downlloading, without having to worry about a burst of throughput from BT lagging the game.

I would think the offosite is true, if you were playing online game such as Q3/Unreal, you would probably want to pause/stop any dl/ul activity that might effect your connection, no matter how much or little, in p2p like Kazaa/Winmx, after you temp stop the transfer, you have to wait inline againe in order for you to resume.

On Bt, you have the ability to pause or temp cancel the download, after you finish your gaming or what not, all you have to do is restart or click on the same seed again and it will resume where you left off and without delay or wait inline.

You do have a point there pcguy. Even if a number of games don't use that much bandwidth.

I really like the ability to see detailed statistics Azureus. I just found another feature in Azureus I really appreciate. The ability to turn off specific files within a batch.

Where I live, my ISP has recently implemented BitTorrent and P2P "throttling". With normal surfing and downloading, the speeds are normal, but when you use a P2P or BitTorrent client, the ISP has software that detects this and throttles down your bandwidth considerably. Needless to say, there have been a lot of people complaining about this.

For example, I'm averaging between 5-10 kbs download speeds with BT, no faster. It is taking me several weeks to download a couple of 4 GB files.

The president of our ISP has even admitted as such that they are throttling down BT and P2P users to generate more bandwidth for other users. You can hear him here (about halfway through the report):

http://www.cbc.ca/nerd/media/tech_bittorrent_pod.mp3

This might very well be the solution that they are using to limit P2P and BT users:

http://www.ellacoya.com/solutions/

I think our ISP is one of the first in our country to implement this (they just started in November). If successful, I wouldn't be surprised if all ISPs in North America would soon implement P2P and BT throttling. This could kill P2P and BT altogether, and you can't even blame the RIAA this time. The ISPs could throttle it back so that you only average 0.1 kbs download speeds and no faster. Most people would just give up instead of waiting for weeks (or even months) to finish downloading something. This would suck, because what about legal uses of BT and P2P?

Anyway, it's interesting that the customer sales reps will deny that any throttling is going on, despite the fact that their president has gone on record as saying they are in fact doing so...

Last edited by allan (2005-04-03 8:41 am)

My ISP sucks, and needs to be beat with a --;

Have you tried changing to a non-standard BT port? like 12345 or something?

Where I live, my ISP has recently implemented BitTorrent and P2P "throttling"...

Boy, that really sucks.  "Invasion of privacy," anyone?

Still...

I've got Azureus.  I don't use it much, but when I do I'd like to get the best speeds possible.

Still, I can't seem to get better than those yellow smilies, and sometimes no better than the blue ones.  AFAIK, this means I'm not getting the best speed possible.

I've got my ports forwarded (I think) and I have no idea what else I can do.  How do I tell if I've got the right ip address for the port forwarding, and are there any other tricks i should use to speed things up?

If anyone could help with this, I'd really appreciate it.
(or should i put it in another forum? only this seemed like the place to ask.)

2) The more likely problem is that you're not properly port forwarded. if you're using the default Azureus port (6881) you need to forward port 6881 to your LAN ip. how to do this varies from router to router.

Are there any common mistakes in port forwarding?  I've followed the directions to the best of my ability, but I'm not getting any improvement.

Airport Extreme with an Airport Extreme base station, if it helps.

is that metallica
tito

New Bittorrent Client

Now spyware free.

anathema wrote:

2) The more likely problem is that you're not properly port forwarded. if you're using the default Azureus port (6881) you need to forward port 6881 to your LAN ip. how to do this varies from router to router.

Are there any common mistakes in port forwarding?  I've followed the directions to the best of my ability, but I'm not getting any improvement.

Airport Extreme with an Airport Extreme base station, if it helps.

If you've got a home network, it's likely you need to go through a firewall (or 2).  If you've got a router, log onto it from your web browser.  The IP address is usually something like 192.168.1.1  but they vary.  I only know how to do this for linksys boxes: click on the "advanced" tab, then on "forwarding."  You've got to tell the router to forward to your computer the requests from the outside on the bittorrent ports. 

So the general flow of things would be:
BitTorrent on ports 6800-6890 -> your router

You need to tell your router to do the following:
BitTorrent on ports 6800-6890 -> your router -> your computer

So.. for this to be a permanent setting, you probably want to turn off DHCP: router-assigned IP addresses given to you every time your computer boots up, usually different than the one you had before.  My linksys router has no problem if I change My network settings from "Using DHCP" to "Manually".  Just enter everything that DHCP gave you manually (Subnet Mask, Router, DNS Servers), except for the IP address, which you should name outside the DHCP range.  So if your router assigns through DHCP 192.168.1.100 - 192.168.1.199, then go ahead and make it 192.168.1.200. 

Back to your router.  On the "forwarding" page, enter the port range for BitTorrent (9800-6890), the IP address to forward them to, and whether or not its TCP or UDP (I'm pretty sure bittorrent is TCP). 

Now... if you're a good net citizen, you've also enabled the software router built in to OS X.  Even if you get your router to forward the BitTorrent traffic to your computer, OS X will ignore it all unless you explicitly tell it not to.  Go to: System Preferences -> Sharing -> Firewall and hit "new" to add an accepted port.  It's pretty straightforward.

I don't know if the airport base stations have firewalls, but if you log onto them with your airport admin application, the firewall settings shouldn't be too hard to find and change, if they exist at all.  You'll know when you've opened up a pathway if BitTorrent goes from a few kB/s (like 3) to a few hundred kB/s (like 300).  Enjoy!  I hope this wasn't too hard to read/understand.

I agree.  Why not capitalize on the bandwidth of those who are capitalizing on the download?  It makes perfect sense to me.