Bastard Pipex have implemtented a 24/7 throttle on P2P traffic, including BT and Emule. BT isn't so much a problem because of encryption in Az and utorrent, but emule has had it for me. I did try Neomule and Sion mods - but they're not going to work unless everyone uses them (why can't the emule developers implement it). At the moment I'm stuck at 20 Kb/s download with emule and 3 months left on this shitty Pipex.

Looks like I'll end up on NTL after all - I can live with a bit of traffic shaping but not 24/7 throttling.

How do they implement the throttleing?

Well it certainly not based on ports, cos I've tried all the normal port tricks. I believe it's something they do with their routers and the only way around it is with encryption. As I've said Bittorrent is OK, but no way with emule.

What really pisses me off most is I'm not even a massive bandwidth hog, a lot of the time I'm only uploading anyway and I my connection is 1024/256 which I am more than happy with. This throttling is across the board AFAIK with Pipex.

Its called traffic shaping rather than throttling generally, and in involves analysising data packets and port usage and then slowing the connection speed via that port if its found to be non-http/smtp/etc. it basically comes down to the construction of TCP packets and analysising its header.

Encrypting the packets defeats the routers that do it because it can not determine if its legitimate traffic or not.

Whatever it's called spud it is still bollox.

Anyway I've been trying Neomule 4.11 with that test file posted over at FH and it certainly works. Now all we (I) have to do is convince the emule developers to implement it so all clients and mods have it.