This forum has been archived. All content is frozen. Please use KDE Discuss instead.

ktorrent and Hughesnet satellite

Tags: None
(comma "," separated)
gary_lankford
Registered Member
Posts
16
Karma
0

ktorrent and Hughesnet satellite

Thu Jul 19, 2007 5:12 am
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!
johnjaylward
Registered Member
Posts
63
Karma
0
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.

gary_lankford wrote: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!
gary_lankford
Registered Member
Posts
16
Karma
0

Fri Jul 20, 2007 7:30 am
Thanks for taking the time to reply. I confess openly that most of this networking stuff just confuses the heck out of me. :) Perhaps my density has some to do with age.

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!
johnjaylward
Registered Member
Posts
63
Karma
0

Fri Jul 20, 2007 2:06 pm
gary_lankford wrote: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.

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(?).

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.

gary_lankford wrote: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.

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.
gary_lankford
Registered Member
Posts
16
Karma
0

Fri Jul 20, 2007 9:53 pm
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

DW6000/7000 or HN7000S NAT router

Note: A router is not the best choice for this type of network. A better choice would be a hard wired hub or a wireless access point. If you have no choice but to use a router follow the steps below to set it up to work with your network.

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. Disable the built in DHCP server.
......2. Set its LAN IP address to 192.168.0.254.
......3. Set its LAN Subnet Mask to 255.255.255.0.
......4. Set its LAN Default Gateway to 192.168.0.1.
Note: Not all routers will have these settings. If yours does not you should consider purchasing either a hard wired hub or a wireless access point. Also you may loose connectivity to your router after making these changes. If at any point you want to reset your router, most routers have a reset button on the back. Press and hold the reset button for at least 15 seconds. This will reset the router to its original factory settings and allow you to regain connectivity to it.

4. Plug the DW6000/7000 or HN7000S into your router.
Note: Do NOT plug into the "WAN / Internet" port on your router.

5. Reboot your computer to renew its IP address.

6. At this point you should have internet connectivity. If you don't recheck each step carefully. You can also try resetting your router's settings and starting over. Most routers include a reset button on the back for this purpose. Press and hold the reset button for at least 15 seconds.

7. To ensure proper performance, run the LAN Client Configuration Utility (LCCU) on each PC connected to the DW6000/7000 or HN7000S. For help with this Click Here

8. This concludes the network setup. Anytime you want to access the router's internal webpage browse to 192.168.0.254. Anytime you want to access the DW6000/7000 or HN7000S's internal web page browse to 192.168.0.1


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...
johnjaylward
Registered Member
Posts
63
Karma
0

Sat Jul 21, 2007 3:17 am


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.
gary_lankford
Registered Member
Posts
16
Karma
0

Sat Jul 21, 2007 5:43 am
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:

Listed below are two options to set up a WRT54G series wireless router, including the WRT54G, WRT54GL, WRT54GS, WRT54GX, and WRT54GC, with a DW6000/DW7000 unit that has NAT enabled (the DW6000 Consumer, DW7000 Home, and DW7000 Pro without Static IP).

Both sets of instructions assume the WRT54G is set to it's factory default settings, or the settings it had when it was new. If your "acquired" WRT54G has been previously used, it may not be set to it's default settings. To return the WRT54G back to it's defaults, power up the router (without anything connected to it) and press the RESET button on the back of the router for 10 seconds. Then power down the router.

Option 1. WRT54G as a Switch with Wireless Access Point (The preferred, but more involved setup):

Why would you want to use Option No. 1?
If you have a DW6000/DW7000 with NAT enabled, setting up the WRT54G as a Switch with Wireless Access Point is cleaner configuration networking-wise. Meaning ... You don't need to two NATs, two DHCP servers and two subnets on your home network. The self-hosted HughesNet modems will share the connection to PCs on your LAN and are capable of handing out IP addresses to your machines via DHCP. All you need is a switch to connect the HughesNet modem to wired PCs on your LAN. If you also have Wireless PCs, you need to add in a wireless access point. You can buy a separate switch and an access point, but it will cost you more than just buying a wireless router. Using option no. 1 to set up the WRT54G provides a switch and an access point without adding in a second layer of NAT.


Things may go easier for you if the WRT54G is not connected to your DW6000/DW7000 unit. Also, set the router up using using a desktop PC or laptop with a wired network adapter (NIC).

First, disable any OS (Windows) and software firewalls on all your PCs (and your laptop, if you have one) while you are setting things up.

You should access the WRT54G's setup Pages to change it's IP address to one that is compatible with the DW6000/DW7000's subnet (192.168.0.0) so that you can access the router later on to change settings. To configure the WRT54G, it's best to connect a PC or laptop with a wired NIC, or network card, to a LAN port on the WRT54G using a regular, Cat 5 ethernet cable and then power up the router.

In order to access your WRT54G from your PC/laptop, you need to do two things:
1. The wired NIC on your PC or laptop must have an IP address in the same address range as the default IP given to the WRT54G by Linksys. According to the Linksys manual, the default IP of the router is 192.168.1.1, so you'll need to assign an IP address of 192.168.1.10 with a subnet mask of 255.255.255.0 This address assignment is temporary. In WinXP right-click "My Network Places" on the desktop, select "Properties", right-click "Local Area Connection", select "Properties, scroll down and double-click Internet Protocol (TCP/IP), and "Use the following IP address:" of 192.168.1.10 and subnet mask of 255.255.255.0
2. If you have the Browser (IE6) Proxy set up on the PC, disable it. To un-Proxy your browser (in IE6), go to "Tools - Internet Options", press the "LAN Settings.." button on the Connections Tab, and then uncheck "Use a proxy server for your LAN...". Then "OK" your way out.

Then (on the PC/laptop) browse to the router's configuration screen by typing in 192.168.1.1 as the URL. Leave the user name field blank and enter the password of "admin".

On the "Wireless - Basic Wireless Settings Tab":
The default wireless network name (SSID) broadcast by the WRT54G is linksys, and you should consider changing it to a name of your own.

LAN Settings:
Go to "Network setup" on the "setup - Basic setup Tab" and change the LAN IP address to 192.168.0.254 with a subnet address of 255.255.255.0 and disable the DHCP Server. Press "Save Settings". You'll lose the browser connection to the router's setup Pages when you save the changes, but that's OK. Just close the browser window.

From this point on, you will need to use the IP address of 192.168.0.254 in your Browser to access the WRT54G. The Proxy must be OFF or you can place the address, 192.168.0.254, in the Exceptions List in "Proxy Settings" (in IE6).

You can now set all of your wired PCs' network cards (the "Local Area Connection" in "Network Connections") and also any wireless PC's/laptop's wireless adapters ("Wireless Network Connection") to receive their IP and DNS IP addresses automatically via DHCP from the DW6000/DW7000, or you can set static addresses such as:

IP address: 192.168.0.2
Subnet mask: 255.255.255.0
Gateway: 192.168.0.1
Preferred DNS: 192.168.0.8
Alternate DNS: 198.77.116.12

The next PC is set up the same way, except it would have an IP address of 192.168.0.3, etc.

Run a Cat 5 cable from your DW6000/DW7000 to a LAN port on the router. Plug the remaining wired PCs into LAN ports on the WRT54G. Then power up the DW6000/DW7000 unit if it is not already on.

On your wireless PCs/laptops, right-click "My Network Places" on the desktop, select "Properties", right-click "Local Area Connection" in the "Network Connections" window, and "Disable" the connection. Make sure the "Wireless Network Connection" is "Enabled".

Reboot the wired and wireless computers. After rebooting the wireless machines, double-click on the wireless connection icon in the System Tray. Verify you have a signal from the router's access point and you are connected to the wireless network. Check the signal strength. If necessary, you may have to use your laptop's wireless adapter utility to "select" the wireless network name (SSID) broadcast by the WRT54G and "connect" to it.

Then try browsing the internet on each PC/laptop. Ping a server on the internet. If you are successful...

Enable the Proxy in the Browser on your PCs/laptops. To Proxy your Browser (in IE6), go to "Tools - Internet Options", press the "LAN Settings.." button on the Connections Tab, and check "Use a proxy server for your LAN...". Then press the "Advanced..." button and enter 192.168.0.1, port 87 for the "HTTP:" setting only. Enter "www.direcwaysupport.com" (DW6000 units) or "www.systemcontrolcenter.com" (DW7000 units);192.168.0.254;192.168.0.*" (without the quotes) in the Proxy "Exceptions" list and then "OK" your way out.

Re-enable the firewalls on the PCs/laptops. Hopefully everything will still work, but you may need to adjust some firewall settings if it doesn't.

Finally (if you wish), go back into the WRT54G's configuration to enable WEP/WPA/WPA2 encryption on the router with matching encryption on the wireless adapter on the PCs/laptop. Try WPA-PSK (Pre Shared Key) and use the same "passphrase" on the router and the PCs/laptop.

Option 2. WRT54G as a Wireless Router (The easy setup):

Why would you want to use Option No. 2?
The bottom line is that the WRT54G is so easy to install this way, and the performance hit by having a double-NAT on your home LAN is negligible. The double NAT doesn't seem to noticeably affect browsing and downloading/uploading files to/from the internet. Just cable the LAN port on the DW6000/DW7000 unit to the Internet (WAN) port on the WRT54G, the wired PCs to the router's LAN ports, and the router will work right out of the box with it's factory default settings. The wireless PCs will connect to the default wireless network name (SSID = "linksys") broadcast by the router's access point. Another reason for you to consider Option No. 2 is because you would be able set the router to filter access to the internet from selected PCs on your LAN. For example, you can restrict access to specific sites, or block access to sites (entirely or by time of day). This would be useful if you want to restrict your kid's access to the internet from their PCs.


Disable the firewalls on your wired and wireless PCs.

Set the wired PC's network cards and the wireless PC's wireless adapters to obtain their IP and DNS server IP addresses automatically.

Take the WRT54G out of the box, cable the LAN port on the DW6000/DW7000 to the router's WAN or Internet Port, and plug any wired PCs into the router's LAN (numbered) ports.

Then power up the router.

Reboot your wired and any wireless PCs. The comments regarding wireless PCs in Option 1 above still apply.

You should be able to browse the internet, ping a server, get your email, etc.

If you want to access your router's setup pages, browse to 192.168.1.1 . As mentioned in Option 1, the Proxy in the browser must be disabled, or you can place the address 192.168.1.1 in your Proxy Settings Exception List.

Re-enable your firewalls.


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!
gary_lankford
Registered Member
Posts
16
Karma
0

Sat Jul 21, 2007 5:51 am
For $20/month more you can get a static IP from Hughesnet. Since I'm not paying the first $70/month, I really don't think I can ask the people who are to pay $20 more... :)

I just have to live with this system, but I can try and tweek it a bit!


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot]