When I am running Ktorrent it takes about 30 seconds for a web page to open, in stead of 1 or 2 seconds. The download speed is very slow 200B/s and the status of most of the torrents is “Stalled”. If have opened TCP and UDP ports 36477 4444 6881, 7881, 8881 and added them to the port forwarding list in my router. No difference. Any body know what I am missing.
On Mon, 05 Sep 2011 17:26:03 +0000, 2fry wrote:
> When I am running Ktorrent it takes about 30 seconds for a web page to
> open, in stead of 1 or 2 seconds. The download speed is very slow 200B/s
> and the status of most of the torrents is “Stalled”. If have opened TCP
> and UDP ports 36477 4444 6881, 7881, 8881 and added them to the port
> forwarding list in my router. No difference. Any body know what I am
> missing.
Your ISP may be throttling your connection.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
If the ports are blocked ktorrent will show a yellow warning triangle in the status bar, else it will show “DTH: XXX nodes, YYY tasks”.
Your ISP may be throttling you, but I doubt it would throttle you that much. Search the internet for complaints against your ISP, you may get your answer there.
Also take a look at ktorrent’s network configuration, specially the upload speed limit and max connection configs, these usually can impact heavily on your and other users download speeds in the same LAN.
Did you open those ports in the SUSE firewall?
It’s not unusual for a torrent to affect other connections. Reasons include:
Hogging the upload channel, particularly for ADSL. This affects requests for links on a web page, e.g. images, JavaScript.
Running the NAT firewall (usually in the router) out of connection tracking slots
You might want to see what options the torrent software give you to limit bandwidth use (in each direction).
Yes, ports are open in the firewall. Sorry about the lack of clarity.
As has been said, it’s normal that you would experience a slow down of other traffic when a torrent application is running, particularly if it is uploading or downloaded at a unlimited setting. Tweak the upload and download settings so they are a little under your max. I have always found azureus less aggressive in this regard.
FYI: Download speeds are subjective. You should report only on torrents you know are well supplied, such as:
http://download.documentfoundation.org/libreoffice/stable/3.4.3/rpm/x86/LibO_3.4.3_Linux_x86_install-rpm_en-US.tar.gz.torrent
Have you tried disabling DHT and/or using protocol encryption?
Disabling DHT is a good idea although I doubt it’s the source of the problem. Protocol encryption should be disabled by default in Ktorrent but it won’t hurt to try 
Anyway IMHO the most probable cause of problems is that Ktorrent eats up all your bandwidth, that’s why the pages are slowed down. As already suggested limit your upload and download speeds in Ktorrent or download what You need at night and stop all the already downloaded torrent so they won’t be uploading any more.
Best regards,
Greg
The router could have a small Nat table, I know this happens with the fios router, source of many complaints.
The router should have some way of showing this info.
I have tried the default settings (DHT is off and no encripting) with 100kbit/s upload limit and 1 kbit/s download limit. I have a 20 Megabit/s internet connection and I have tested the download speed. As stated on my original post
(The download speed is very slow 200B/s and the status of most of the torrents is “Stalled”) 200 Bytes/sec. THIS IS SNAIL SPEED!
After reading several pages on the Internet I found that my ISP “Comcast” blocks all BitTorrent files. I did not know this was possible. Some people state that a good encryption program can prevent this but all the current one have been decoded. Another person stated that he uses port 80 which works for him. I tried that but another program is using it, probably TCP/IP. Is there any way to determine which program is using which port? Are there any other ports or encryption systems I can try? All this does not explain why fire fox loads pages 100 times slower when Ktorrent is running. Cna anyone suggest a better BitTorrent program?
Thanks for all your suggestions
I thought Comcast was ordered to allow bittorrent by the FCC? Oh well, you might consider a different provider. Comcast makes its own rules as it goes along, and I don’t know why people do business with them.
Torrent uses well known ports. Probably Comcast throttles your entire channel when it detects torrent in use.
A good ISP is a absolute must have. Many are lured in to the realms of darkness by price. Don’t be.
Bad ISPs - VuzeWiki
Torrent junkies often recommend using ports up the range like 60000
Port forwarding - VuzeWiki
Avoid traffic shaping - VuzeWiki
My suggestion was to turn encryption ON. I found it in the FAQ - KTorrent, and it did help with the slow web page loading on my system. There are other ideas there you might try, too.
The other thing you can try is a different client. Ktorrent is buggy. I finally gave up on it and switched to Transmission, and have not had any of the problems with it that I did with Ktorrent.
Well looks like I am in a bit of a pickle. I have tried Vuze and GBitorrent with the same results. The test in Vuze passed the connections but had some errors. I could not get Transmission to launch so I am not sure what I am doing wrong or if there is a resource missing. I have no other choice for a 1.5Mbit/s ISP provider unless I want to spend $300.00 a month.
Here is what the network status in Vuze comes back with…
Test starting
Default public address is 98.207.40.247
Testing routing for the following interfaces:
wlan0/wlan0: 192.168.200.12
Can’t run ping test as not supported
Can’t run trace route test as not supported
0 NAT devices found
No SOCKS proxy found
No HTTP proxy found
No explicit bind address set
Testing HTTP outbound
Test successful
Testing TCP outbound
Test successful
Testing UDP outbound
Test successful
Testing TCP port 62223 inbound
Test successful
Testing UDP port 62223 inbound
Sending outbound packet and waiting for reply probe (timeout=5000)
Sending completion event
Test successful
1 public/external addresses found
98.207.40.247
AS details: as=33651,asn=CMCS - Comcast Cable Communications, Inc., bgp_prefx=98.207.0.0/16[/98.207.0.0-/98.207.255.255]
Distributed protocol test
Incoming routing established for 103702B7C5DF9F6CEE346F47AB37E9AF8DD9689C
Searching 128 contacts for 8 test targets
Making outbound connection to /174.117.175.94:48928
(LL 1) Outbound connect start
Making outbound connection to /68.230.65.36:43327
(LS 2) Outbound connect start
Making outbound connection to /184.99.137.175:30923
(LL 3) Outbound connect start
Making outbound connection to /108.56.146.191:30669
Got incoming connection from /174.117.175.94:62695
(RL 5) Inbound connect start
(RL 5) Inbound connect success
(LS 2) Outbound connect success
(RL 5) Incoming message received: BT_HANDSHAKE
(LS 2) Outgoing message sent: BT_HANDSHAKE
(LS 4) Outbound connect start
Making outbound connection to /174.118.99.249:21620
Making outbound connection to /86.212.242.43:6881
(RL 5) Outgoing message sent: BT_HANDSHAKE
(RL 5) Outgoing message sent: BT_BITFIELD
Making outbound connection to /71.185.203.19:20202
Got incoming connection from /68.230.65.36:4515
(RL 9) Inbound connect start
(RL 9) Inbound connect success
(LS 6) Outbound connect start
(LS 8) Outbound connect start
(LL 7) Outbound connect start
(LS 2) Incoming message received: BT_HANDSHAKE
(RL 9) Incoming message received: BT_HANDSHAKE
Making outbound connection to /71.193.174.98:41286
(LL 1) Outbound connect success
(LS 10) Outbound connect start
(LS 2) Outgoing message sent: BT_BITFIELD
(RL 9) Outgoing message sent: BT_HANDSHAKE
(RL 9) Outgoing message sent: BT_BITFIELD
(LL 1) Outgoing message sent: BT_HANDSHAKE
(LS 2) Incoming message received: BT_BITFIELD
Got incoming connection from /108.56.146.191:62015
(RL 11) Inbound connect start
(RL 11) Inbound connect success
(LS 4) Outbound connect success
(RL 9) Incoming message received: BT_BITFIELD
(RL 11) Incoming message received: BT_HANDSHAKE
(LS 10) Outbound connect success
(LS 4) Outgoing message sent: BT_HANDSHAKE
(RL 11) Outgoing message sent: BT_HANDSHAKE
(RL 11) Outgoing message sent: BT_BITFIELD
(LS 10) Outgoing message sent: BT_HANDSHAKE
(LS 8) Outbound connect success
Got incoming connection from /71.193.174.98:50010
(RL 12) Inbound connect start
(RL 12) Inbound connect success
(LS 8) Outgoing message sent: BT_HANDSHAKE
(RL 12) Incoming message received: BT_HANDSHAKE
(RL 12) Outgoing message sent: BT_HANDSHAKE
(RL 12) Outgoing message sent: BT_BITFIELD
(LS 10) Incoming message received: BT_HANDSHAKE
(LS 4) Incoming message received: BT_HANDSHAKE
(RL 5) Incoming message received: BT_BITFIELD
(LL 1) Incoming message received: BT_HANDSHAKE
(LL 1) Incoming message received: BT_BITFIELD
(LS 10) Incoming message received: BT_BITFIELD
(LS 10) Outgoing message sent: BT_BITFIELD
(LS 4) Outgoing message sent: BT_BITFIELD
(LL 1) Outgoing message sent: BT_BITFIELD
Got incoming connection from /174.118.99.249:61139
(RL 13) Inbound connect start
(RL 13) Inbound connect success
(RL 13) Incoming message received: BT_HANDSHAKE
(LS 4) Incoming message received: BT_BITFIELD
(RL 13) Outgoing message sent: BT_HANDSHAKE
(RL 13) Outgoing message sent: BT_BITFIELD
(RL 11) Incoming message received: BT_BITFIELD
Got incoming connection from /71.185.203.19:50094
(RL 14) Inbound connect start
(RL 14) Inbound connect success
(RL 14) Incoming message received: BT_HANDSHAKE
(RL 14) Outgoing message sent: BT_HANDSHAKE
(RL 14) Outgoing message sent: BT_BITFIELD
(LL 3) Outbound connect success
(LL 7) Outbound connect success
(LS 6) Outbound connect success
(LL 3) Outgoing message sent: BT_HANDSHAKE
(LL 7) Outgoing message sent: BT_HANDSHAKE
(LS 6) Outgoing message sent: BT_HANDSHAKE
Got incoming connection from /86.212.242.43:50118
(RL 15) Inbound connect start
(RL 15) Inbound connect success
(RL 12) Incoming message received: BT_BITFIELD
(LS 8) Incoming message received: BT_HANDSHAKE
(RL 15) Incoming message received: BT_HANDSHAKE
(LS 8) Incoming message received: BT_BITFIELD
Got incoming connection from /184.99.137.175:58305
(RL 16) Inbound connect start
(RL 16) Inbound connect success
(RL 16) Incoming message received: BT_HANDSHAKE
(LS 8) Outgoing message sent: BT_BITFIELD
(RL 15) Outgoing message sent: BT_HANDSHAKE
(RL 15) Outgoing message sent: BT_BITFIELD
(RL 16) Outgoing message sent: BT_HANDSHAKE
(RL 16) Outgoing message sent: BT_BITFIELD
(RL 14) Incoming message received: BT_BITFIELD
(RL 15) Incoming message received: BT_BITFIELD
(RL 13) Incoming message received: BT_BITFIELD
(LS 6) Incoming message received: BT_HANDSHAKE
(LL 7) Incoming message received: BT_HANDSHAKE
(LL 3) Incoming message received: BT_HANDSHAKE
(LS 6) Incoming message received: BT_BITFIELD
(LL 7) Incoming message received: BT_BITFIELD
(LL 3) Incoming message received: BT_BITFIELD
(LS 6) Outgoing message sent: BT_BITFIELD
(LL 7) Outgoing message sent: BT_BITFIELD
(LL 3) Outgoing message sent: BT_BITFIELD
(RL 16) Incoming message received: BT_BITFIELD
Making outbound connection to /173.74.135.244:34470
(LL 17) Outbound connect start
Got incoming connection from /173.74.135.244:4152
(RL 18) Inbound connect start
(RL 18) Inbound connect success
(RL 18) Incoming message received: BT_HANDSHAKE
(RL 18) Outgoing message sent: BT_HANDSHAKE
(RL 18) Outgoing message sent: BT_BITFIELD
(LL 17) Outbound connect success
(LL 17) Outgoing message sent: BT_HANDSHAKE
(RL 18) Incoming message received: BT_BITFIELD
(LL 17) Incoming message received: BT_HANDSHAKE
(LL 17) Incoming message received: BT_BITFIELD
(LL 17) Outgoing message sent: BT_BITFIELD
Got incoming connection from /89.131.73.121:4640
(RL 19) Inbound connect start
(RL 19) Inbound connect success
(RL 19) Incoming message received: BT_HANDSHAKE
(RL 19) Outgoing message sent: BT_HANDSHAKE
(RL 19) Outgoing message sent: BT_BITFIELD
(RL 19) Incoming message received: BT_BITFIELD
Searching complete, 9 targets found
Status: sessions=19, out_attempts=9, out_connect=9, in_connect=10
Destroying tester
Results
Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Test complete
Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Seed,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Outbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Inbound,Leecher,connected, hand sent, hand recv, bitf sent, bitf recv
Incoming routing destroyed for 103702B7C5DF9F6CEE346F47AB37E9AF8DD9689C
(LL 1) Outgoing message sent: BT_HAVE
(LS 2) Outgoing message sent: BT_HAVE
(LL 3) Outgoing message sent: BT_HAVE
(LS 4) Outgoing message sent: BT_HAVE
(RL 5) Outgoing message sent: BT_HAVE
(LS 6) Outgoing message sent: BT_HAVE
(LL 7) Outgoing message sent: BT_HAVE
(LS 8) Outgoing message sent: BT_HAVE
(RL 9) Outgoing message sent: BT_HAVE
(LS 10) Outgoing message sent: BT_HAVE
(RL 11) Outgoing message sent: BT_HAVE
(RL 12) Outgoing message sent: BT_HAVE
(RL 13) Outgoing message sent: BT_HAVE
(RL 14) Outgoing message sent: BT_HAVE
(RL 15) Outgoing message sent: BT_HAVE
(RL 16) Outgoing message sent: BT_HAVE
(LL 17) Outgoing message sent: BT_HAVE
(RL 18) Outgoing message sent: BT_HAVE
(RL 19) Outgoing message sent: BT_HAVE
(LS 6) Closing connection
(RL 13) Closing connection
(RL 11) Closing connection
(LS 4) Closing connection
(LL 1) Closing connection
(RL 9) Closing connection
(LS 2) Closing connection
(LL 17) Closing connection
(RL 18) Closing connection
(RL 16) Closing connection
(LL 3) Closing connection
(LL 7) Closing connection
(RL 15) Closing connection
(RL 14) Closing connection
(LS 8) Closing connection
(RL 12) Closing connection
(LS 10) Closing connection
(RL 5) Closing connection
(RL 19) Closing connection
Hi
It’s an old article but may provide some idea as to why
http://torrentfreak.com/comcast-throttles-bittorrent-traffic-seeding-impossible/
Or google on comcast+traffic shaping+p2p
A lot of people probably just move to a usenet provider that provides
binary files…
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 6 days 1:11, 3 users, load average: 0.23, 0.14, 0.08
GPU GeForce 8600 GTS Silent - Driver Version: 280.13
Although Comcast policies may be an issue, it’s usually only after you’ve been using it awhile and have built your numbers up until you start getting throttled.
Based on my own investigation, I <know> what the issues likely are…
- By default all current Linux kernels are tuned for a relatively low number of simultaneous network connections.
- By default all current Linux kernels are configured to expect high quality network connections with practically no latency and loss (which is rarely the case over wireless and connecting to a multitude of unreliable remote hosts which is what torrent apps do).
I’ve collected all the information across the Internet I can find on how to address these issues…
- How to re-configure TCP Buffers to accomodate larger numbers of high latency connections
- How to configure TCP windows, enable various TCP options to further improve TCP capacity
- How to select and enable a non-default TCP Congestion Control algorithm more suited to non-optimal network connections, eg WiFi, Telco Wireless, Satellite, faster or slower ISP connections, more
At my website
https://sites.google.com/site/4techsecrets/optimize-and-fix-your-network-connection
Short of installing an Enterprise kernel, everything you need to do is there, and applies to all Linux distros, not just openSUSE.
HTH,
Tony
Old news -
April 07, 2010
Court rules against FCC’s Comcast Net neutrality decision
Court rules against FCC’s Comcast Net neutrality decision | The Industry Standard - InfoWorld
Looks like we will need to find another way to share large files.
if anybody wants to test whether or not his ISP is throttling BitTorrent, Glasnost is a good site to test.