![]() Registered Member ![]()
|
I have been reading and trying to learn as much as I can but some things are not as evident as others, at least for me.
It started when I was having trouble acessing the web with Firefox after ktorrent ran for a while, at first I thought it was a program called MoBlock , so I stopped using it, then I though it might be DHT, so I turned that off. In the end it appears it may be the WRt5GS router just can't handle all the requests, so I backed off to more conservative numbers limiting ktorrent to 5 downloads/ipload and seeds at a time with a maximu of 75kbs up and down. I am suppossed to have around 4 mps down and 384 kbs up. I also limited global peers to 125 and 20 per torrent. Anyhow today it ran all day and was still ok so I am on the right track. I also had DHT on all day - everything is lookign good so far. My question is about DHT, I have something like 110 peers and have seen it as high as 10 tasks but other than that don't see where it is giving me much benefit. How do I take advantage of the extra peers when I have no idea what is going on with them? Does Ktorrent use them automatically or must I know what they have? IEven though I read about it on Wikipedia, I feel like I am missing something. I am looking forward to an invite to Oink, perhaps that tracker uses DHT more than the ones I have been using. I do admit I have been downloading pretty lame stuff, so there usually are not too many peers. joe on edit: I wrote too soon, I turned on a third seed and everything started to crawl, even though according to ktorrent I am uploading less than 50kbs. I found dmesg filled up with errors as well. SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.100 DST=24.0.188.110 LEN=66 TOS=0x08 PREC=0x00 TTL=64 ID=40667 DF PROTO=TCP SPT=12000 DPT=15188 WINDOW=429 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00FE233C00FDB5EF) SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.1.100 DST=24.0.188.110 LEN=156 TOS=0x08 PREC=0x00 TTL=64 ID=37864 DF PROTO=TCP SPT=15086 DPT=12000 WINDOW=432 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00FE23F500FD8F27) SFW2-INext-DROP-DEFLT-INV IN=eth0 OUT= MAC=00:20:78:05:73:cb:00:18:f8:72:fa:7d:08:00 SRC=65.188.11.144 DST=192.168.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=15111 PROTO=TCP SPT=12986 DPT=17452 WINDOW=0 RES=0x00 RST URGP=0 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.100 DST=239.255.255.250 LEN=162 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=1900 DPT=1900 LEN=142 SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:20:78:05:73:cb:00:18:f8:72:fa:7d:08:00 SRC=24.0.188.110 DST=192.168.1.100 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=14578 DF PROTO=TCP SPT=54758 DPT=12000 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A00FD7A570000000001030304) SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:20:78:05:73:cb:00:18:f8:72:fa:7d:08:00 SRC=192.168.1.1 DST=192.168.1.100 LEN=343 TOS=0x00 PREC=0x00 TTL=64 ID=50570 PROTO=UDP SPT=1900 DPT=1900 LEN=323 How can I fix this, it goes away when I stop using ktorrent, perhaps a problem with one of my ports? I am using OpenSuse 10.2 |
![]() Registered Member ![]()
|
Some routers do have issues with large number of connections. Limiting that can help, and also turning off DHT can have a benefit, too (since routers seem to handle UDP mappings more poorly)
If you've found 110 peers, then you really don't need DHT's help. DHT helps locate peers without the use of a tracker. This is helpful in circumstances such as: (1) The tracker went down. (2) There is no tracker (trackerless torrent) (3) Sometimes multitracker torrents have disconnected swarms -- i.e. each of the trackers has a different set of peers, so you never get all of them. In these cases, DHT will help you locate more peers. For #1 and #2, DHT is crucial to finding an initial set of peers. In all of these cases, if you have contact to a uTorrent or MooPolice peer, KTorrent 2.1rc1 and higher will be able to find more peers by asking these peers who they know about (Peer Exchange/PEX).
It seems like you're having some sort of networking problem. Try seeding less or drastically lowering the number of maximum connections.
This is just iptables output, showing that you are running a local firewall of some sort that is logging/dropping packets due to its ruleset. Verify in your firewall rules that KTorrent is being allowed to listen/accept connections on a port (12000, it looks like). As long as that's confirmed, these messages are harmless. In addition, check your router configuration and make sure port forwarding for TCP and UDP is set up correctly. Bad port forwarding settings can also lead to more router stress than necessary. |
![]() Registered Member ![]()
|
Thanks,
My grammer was not as clear as it should have been, the 110 peers was through DHT. I will check into setting up the router better. I did seem to luck out last night with one peer as I was getting over 200kbps , far cry from the 1- 2 kbps when I first started. As you can tell, I am new to using broadband connection, and bittorrent. |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft