![]() Registered Member ![]()
|
I'm using Ktorent 2.2 with KDE 3.5.7 on SuSE 10.1 and a 2.8Ghz P4.
My internet connection is through Hughesnet satellite and I have a DW7000 modem. While occasionally downloads are fairly rapid, uploads are most often faster for the same torrent. Even when there are few leechers and several seeders my download speeds are most often very slow (< 1 KB/s) and even when there are seeders on and I am not snubbed torrents are often stalled. I have tried varying port settings, but am currently using 57456 for the 'Port' setting and 4444 for the 'UDP' setting. I have DHT 'on' and port 6881 selected, I am also using the UPnP plugin. I am using Firestarter as my firewall, but have turned it off with no change in ktorrent performance. I have opened the three ports mentioned above as well as the bittorrent range 6881-6889. I see a significant number of blocked connections in the port range 30000-65000 while ktorrent is running, but when I open that port range there is no improvement in performance. I have my router firewall turned off. My problems are probably related to the nature of my satellite internet, but I am wondering if anyone out there has any ideas for optimizing my settings. Thanks for your attention! |
![]() Registered Member ![]()
|
Are you forwarding the ports from your router, or just opening them. If you are not forwarding them, then the packets will just stay at the router.
Also, the UPnP plug-in should handle any port forwarding for you. You should close up all the ports on your router again, and make sure the the routers UPnP options are turned on. Most routers I've seen come with the feature turned off by default for security reasons.
|
![]() Registered Member ![]()
|
Thanks for taking the time to reply. I confess openly that most of this networking stuff just confuses the heck out of me.
![]() My router is a Linksys WRT54GX2 (SRX 200). Before this writing, the firewall was disabled, UPnP was enabled and no ports were forwarded. I have now enabled the router firewall (as you suggested), left UPnP enabled and (if I understand how to do it) have forwarded the ports mentioned previously (even though UPnP is supposed to do that for me(?)). My router also offers the capability of 'port triggering', a concept I understand even less than forwarding and which I have not tried to use. Two things I failed to mention previously are that 1) despite having DHT turned on in the Ktorrent settings the application status shows DHT: off and 2) the application indicates continuously (and still) 'no incoming connections (possibly firewalled)'. A curious aspect of my Hughesnet setup is that the modem is plugged into a LAN port (rather than the internet (WAN) port) so that the router is being used as a hub. This, because Hughesnet says to use a hub or wireless access point, but I already had this router and that is how they say to set up a router for their system. Perhaps this has something to do with Ktorrent's failure to report incoming traffic(?). Many of the torrents I am interested in have very few seeders (or leechers for that matter). They sit stalled waiting for someone to come along (leecher or seeder) who happens to have some part that I don't have. I understand that this is the way it should be. What I have been concerned with is those times when there is data available from peers who I am not snubbed by, but the torrent is still stalled. One particular torrent, where that has been the case, seems to be running faster now. Hopefully, you've got me straightened out. If you have any other ideas, as a result of what I have written, please let me know! Thanks! |
![]() Registered Member ![]()
|
This is a very odd setup and it defeats the firewall of your router. Your internet connection should always be plugged into your WAN connection on the router. Otherwise all the port forwarding/UPnP is useless. Give it a try with the internet connection plugged into the WAN port (you may need to restart the computers to get everything set up properly). You should also try to keep as many ports closed as possible on your router. Unless you are running other services like HTTP or SSH, you should really leave all the ports closed on the router interface. I'm not familiar with Hughsnet at all, but that seems like really bad advice from a security standpoint. Also the port triggering is probably not a feature you need. It is useful with some games that can be played online, but mostly it's not needed. UPnP is supported by many apps now and is becoming the standard for automated port forwarding.
After you try the above, check to see if your computer has it's own firewall running. If it does, than try disabling it, or opening the ports on that firewall (no forwarding needed here, only on the router) John. |
![]() Registered Member ![]()
|
Thanks again!
Be glad you don't know, or have to know, anything about Hughesnet. It should never be considered by anyone with any other internet service better than dial-up available to them. It is better than dial-up, but just barely. Originally, I had my modem plugged into the WAN port. 5 or 6 months ago, in an attempt to improve my internet service, I started Googling and looking through Hughesnet own documentation for a solution. I found this: http://kb.hughesnet.com/al/12/2/1289.htm#DW6000%20NAT%20Router
And, that is the plan I followed. It did seem to improve my performance. I can see that by doing this all router functions that operate inbetween the LAN and WAN ports would be bypassed. Thanks for pointing that out! I've addressed this issue to the folk over on the Hughesnet forum at dslreports.com. I'll wait to see what they have to say... |
![]() Registered Member ![]()
|
Ok, try this setup on the router instead: 1. Disconnect your computer from the DW6000/7000 or HN7000S. You will reconnect it to the network later. 2. Establish communication between your PC and your router. If you are having trouble doing this please contact the manufacture or your router. Note: Do NOT plug into the "WAN / Internet" port on your router. 3. On the router, you will need to make the following changes to the LAN settings or setup. Consult the owner's manual for instructions on how to do this. ......1. Enable the built in DHCP server. ......2. Set its LAN IP address to 192.168.5.1. ......3. Set its LAN Subnet Mask to 255.255.255.0. ......4. Set its LAN Default Gateway to 192.168.5.1. (may not have to do this with DHCP enabled) ......5. Set up the WAN connection to use DHCP to get it's address Most likely the problem you were having before you made the changes was due to the fact that hughesnet already had you behind a NAT which was on the same subnet that the router expected to be your internal network. Most ISPs assign their clients world accessible IPs, but it looks like hughesnet only provides you with NAT access. That's a pretty cheep and sloppy implementation for an ISP to give you, especially since they created the NAT on such a common subnet for private networks. Changing the internal subnet to anything other than 192.168.0.0/24 i.e. 192.168.5.0/24 should allow you to use the router with all the features enabled, but since hughesnet has you behind a NAT network already you may find that things like bittorrent don't work all that well since they would have to forward that traffic to you. Good luck with the setup. John. |
![]() Registered Member ![]()
|
Hey, thanks again John for taking a look at all that! I'm going to have to digest just a little bit before I go on...
This is the explanation I got from a guy on the Hughesnet forum:
They seem to be a bit touchy on the subject of torrents over there, and since this is a torrent forum, I thought this might be the place to come. Looks like I was right, cause I sure got some great help! Yeah, I think you got it figured, Hughesnet sucks! |
![]() Registered Member ![]()
|
Registered users: Bing [Bot], Google [Bot]