[nflug] deluge bit torrent parameters

SilverBear silverbear1 at sblinux.org
Tue Feb 10 11:35:14 EST 2009


Hi Joe,

Sounds like port forwarding to your router is just what the doctor ordered!

Other stuff:
+ My bad: I should have told you to run "netstat --listen" while your bitorrent client was running. Likewise an nmap command.
+ IMO, it would be quicker and more accurate to add some parameters to the nmap command For example, if you are testing a port like 51666, try this command:

nmap -sT -p 51000-52000 127.0.0.1

If you try it while you're running your Torrent client, it should report 51666 as open. When you're not running the Torrent client, the same command should report:
All 1001 scanned ports on localhost (127.0.0.1) are closed

That's for localhost --your machine. Put in the address of your router instead of 127.0.0.1 to run the same test for that port range on that machine.

More info:
http://insecure.org/

but if it's working now, why bother with more tests? ;-)

John


> -----Original Message-----
> From: josephj at main.nc.us
> Sent: Tue, 10 Feb 2009 00:50:05 -0500
> To: nflug at nflug.org
> Subject: Re: [nflug] deluge bit torrent parameters
> 
> I forwarded my port in the router (per silverbear) and my download speed
> instantly doubled or better!
> 
> But, following the rest of your instructions, I get:
> 
> bigbird at sananda:~/pq$ sudo nmap 72.75.240.48
> 
> Starting Nmap 4.53 ( http://insecure.org ) at 2009-02-10 00:41 EST
> All 1714 scanned ports on pool-72-75-240-48.bflony.east.verizon.net
> (72.75.240.48) are closed
> 
> Nmap done: 1 IP address (1 host up) scanned in 3.715 seconds
> bigbird at sananda:~/pq$
> 
> And, just for the heck of it:
> 
> bigbird at sananda:~/pq$ sudo nmap 192.168.1.46
> 
> Starting Nmap 4.53 ( http://insecure.org ) at 2009-02-10 00:45 EST
> All 1714 scanned ports on 192.168.1.46 are closed
> 
> Nmap done: 1 IP address (1 host up) scanned in 6.942 seconds
> bigbird at sananda:~/pq
> 
> So I'm not sure what I did or why it seems to have worked.
> 
> Can you make sense of this for me?
> 
> TIA
> 
> Joe
> 
> Cyber Source wrote:
>> Your router is blocking the port.
>> 1. Select the port in your app you want to use or the one they suggest.
>> 2. Login to your router and forward the port from above to your IP
>> address (or hostname if capable).
>> 
>> You can test this by getting your public IP (http://whatismyip.com),
>> then run "nmap yourpublicip" and if the app is running, it should show
>> that the port mentioned is open.
>> 
>> Joe wrote:
>>> I really like deluge.  The newest release is a bit better about not
>>> totally hogging the bandwidth.
>>> 
>>> I've also been using transmission.
>>> 
>>> Both programs work (I don't run them at the same time.)  But they both
>>> give me messages about the port being closed.  The transmission FAQ
>>> talks about this saying that if the port is open then more peers can
>>> find you and share more data.  I followed the instructions for allowing
>>> it, but it still says closed. I ran sudo iptables -L and it comes
>>> back empty.  I am not running a
>>> firewall.  I have security set to none in my dsl modem/router/wireless.
>>> 
>>> Why is it still closed and how do I open it?  Is it safe to do so?
>>> 
>>> In transmission preferences->network, it tests the port and says it's
>>> closed.
>>> 
>>> I'm using Verizon DSL with a Westel 327W modem/wireless router.
>>> kubuntu hardy  on a Centrino Duo Notebook.
>>> 
>>> TIA
>>> 
>>> Joe
>>> 
>>> Matthew Koerner wrote:
>>> 
>>>> Hey Joe,
>>>>  Transmission does run great, i concur with John. It has never
>>>> crashed yet
>>>> on me.
>>>> Matthew
>>>> 
>>>>> Hi Joe.
>>>>> 
>>>>> Actually, bandwidth setting could be the issue. My websurfing and
>>>>> that of
>>>>> the family computer on the same router/DSL line improved markedly
>>>>> when I
>>>>> throttled back UL speed.   TCP/IP needs to upload packets  in order
>>>>> to
>>>>> download packets, so choked UL bandwidth can definitely hamper DL
>>>>> bandwidth.  See this page for calculating your settings:
>>>>> http://infinite-source.de/az/az-calc.html
>>>>> 
>>>>> I used Deluge for about a year, in preference to KTorrent or Azureus.
>>>>> Lately I'm liking Transmission.
>>>>> Light-weight, and it doesn't lock up or crash as often as Deluge was
>>>>> doing. I started using it in Pardus, but Now I'm running it in
>>>>> Mepis and
>>>>> Ubuntu as well --no problems so far, after about two-three months.
>>>>> 
>>>>> John
>>>>> 
>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: josephj at main.nc.us
>>>>>> Sent: Sat, 03 Jan 2009 13:52:21 -0500
>>>>>> To: nflug at nflug.org
>>>>>> Subject: [nflug] deluge bit torrent parameters
>>>>>> 
>>>>>> I'm starting to use deluge for large files.
>>>>>> 
>>>>>> What I'm finding is that is I start even one or two torrents, I
>>>>>> lose the
>>>>>> use of the Internet for anything else.
>>>>>> I've tried limiting it to one or two torrents at a time and
>>>>>> throttling
>>>>>> the upload and download speeds to way less than bandwidth.
>>>>>> No luck.
>>>>>> 
>>>>>> What about maximum connections or other settings?
>>>>>> 
>>>>>> I tried setting maximum connections to 50 then 60 and - at least
>>>>>> for the
>>>>>> moment, that seems to work.
>>>>>> 
>>>>>> Any idea what an "optimal" value would be?
>>>>>> 
>>>>>> When I left Max Connections unlimited, it looked like I kept getting
>>>>>> disconnected from both ISP's.
>>>>>> 
>>>>>> Do you think this was coincidence or theirs servers getting upset
>>>>>> with
>>>>>> me.
>>>>>> 
>>>>>> 
>>>>>> I have either dsl 860/128 all to myself, or, sometimes cable
>>>>>> 300+/?, so
>>>>>> bandwidth is not what's doing it.
>>>>>> 
>>>>>> Joe
>>>>>> 
>>>>>> kubuntu hardy, Centrino Duo 1.6GHz, wireless Westel 327G, 1GB ram,
>>>>>> plenty of USB HDD space.
>>>>>> 
>>>>>> _______________________________________________
>>>>>> nflug mailing list
>>>>>> nflug at nflug.org
>>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>> 
>>>>> ____________________________________________________________
>>>>> Receive Notifications of Incoming Messages
>>>>> Easily monitor multiple email accounts & access them with a click.
>>>>> Visit http://www.inbox.com/notifier and check it out!
>>>>> _______________________________________________
>>>>> nflug mailing list
>>>>> nflug at nflug.org
>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>> 
>>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> nflug mailing list
>>> nflug at nflug.org
>>> http://www.nflug.org/mailman/listinfo/nflug
>>> 
>> _______________________________________________
>> nflug mailing list
>> nflug at nflug.org
>> http://www.nflug.org/mailman/listinfo/nflug
>> 
> 
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug


More information about the nflug mailing list