Yet another bittorrent thread
 

Alright. So idownloaded the rpm, and installed it. Now I have no idea how to get it to run and/or operate a torrent file. What exactly do I have to do?
f.y.i. Fedora corse 2, and version 4.0.4 bittorrent

EDIT: nevermind, I got it to run, but now it won't download. it just sits there at 0%, and 0.0 downloaded

terminal version:
GUI version:

Do you get on the internet through a router or firewall? You may have to foreward a port (the default 6881 is blacklisted by most trackers too). Do the torrents that you're trying have any seeds or leechers besides yourself (I don't know how new you are to Bittorrent)?

new enough to only be able to answer the firewall question, which si a yes, I have a firewall

If you have a firewall, then its probably blocking traffic on the prot you need to have open to make bittorrent work. If you've used other file sharing methods before and found that things were slow because you were "unconnectable" that is why. You need to be open for BT to work.

Saying that, I don't know what your firewall works like, so you'd know better than I. There must be a way of forewarding a few ports with it, though. For example, I have a Linksys BEFSR41 router (and its flaky, but anyways). With the Linksys, I have to open a browser and log in to 192.168.1.1. I believe that D-Link's use 192.168.0.1. But you get the picture. I put that address in the address bar of the browser and go to it. A login box pops up and you have to put in the admin password, which by default is "admin". If you have one of these, change it once you're in, just to be sure (routers are dumb, but they're still hackable). On my router, I'd pick the "advanced" tab and then the "forwarding" tab. On that tab, I'd then input the IP of my machine (good to have static IP's on your network for filesharing, BTW) and the port I wanted "forwarded". Check that TCP isbeing forwarded. If you use a UDP tracker once in a while, you can check off UDP as well. Click "apply" and you should now be able to ping right through to the specified port from outside (I test this with a site like Steve Gibson's grc.com's "Shields Up"). One thing you're going to want to do, though, is to change the port used in the bittorrent conf file (pick something with a high number but lower than 65000). That'll be up to you,. as I went with Azureus a long time ago.

There are lots of users of the original client and its offshoots though. Anyone?

***bump***

Didn't want to make a new thread.

I'm having this problem too...I've done what was recommended for my Linksys router, but I'm using btcurses for my bt client.

How do I set it up so that it uses another port to d/l on?

thanks

I haven't used the client in ages, but usually, you can change everything in the config file with a text editor.

Do you know where the config file lies?

I only found the ./bin file.

thanks

I use the btdownloadcurses.bittorrent client from the command line....


arguments are -
--max_uploads <arg>
the maximum number of uploads to allow at once.
(defaults to 7)

--keepalive_interval <arg>
number of seconds to pause between sending keepalives
(defaults to 120.0)

--download_slice_size <arg>
How many bytes to query for per request. (defaults to
16384)

--request_backlog <arg>
how many requests to keep in a single pipe at once.
(defaults to 5)

--max_message_length <arg>
maximum length prefix encoding you'll accept over the
wire - larger values get the connection dropped.
(defaults to 8388608)

--ip <arg>
ip to report you have to the tracker. (defaults to '')

--minport <arg>
minimum port to listen on, counts up if unavailable
(defaults to 6881)

--maxport <arg>
maximum port to listen on (defaults to 6999)

--responsefile <arg>
file the server response was stored in, alternative to
url (defaults to '')

--url <arg>
url to get file from, alternative to responsefile
(defaults to '')

--saveas <arg>
local file name to save the file as, null indicates
query user (defaults to '')

--timeout <arg>
time to wait between closing sockets which nothing has
been received on (defaults to 300.0)

--timeout_check_interval <arg>
time to wait between checking if any connections have
timed out (defaults to 60.0)

--max_slice_length <arg>
maximum length slice to send to peers, larger requestsare ignored (defaults to 131072)

--max_rate_period <arg>
maximum amount of time to guess the current rate
estimate represents (defaults to 20.0)

--bind <arg>
ip to bind to locally (defaults to '')

--upload_rate_fudge <arg>
time equivalent of writing to kernel-level TCP buffer,
for rate adjustment (defaults to 5.0)

--display_interval <arg>
time between updates of displayed information (defaults
to 0.5)

--rerequest_interval <arg>
time to wait between requesting more peers (defaults to
300)

--min_peers <arg>
minimum number of peers to not do rerequesting
(defaults to 20)

--http_timeout <arg>
number of seconds to wait before assuming that an http
connection has timed out (defaults to 60)

--max_initiate <arg>
number of peers at which to stop initiating new
connections (defaults to 35)

--max_allow_in <arg>
maximum number of connections to allow, after this new
incoming connections will be immediately closed
(defaults to 55)

--check_hashes <arg>
whether to check hashes on disk (defaults to 1)

--max_upload_rate <arg>
maximum kB/s to upload at, 0 means no limit (defaults
to 0)

--snub_time <arg>
seconds to wait for data to come in over a connection
before assuming it's semi-permanently choked (defaults
to 30.0)

--spew <arg>
whether to display diagnostic info to stdout (defaults
to 0)

--rarest_first_cutoff <arg>
number of downloads at which to switch from random to
rarest first (defaults to 4)

--min_uploads <arg>
the number of uploads to fill out to with extra
optimistic unchokes (defaults to 4)

--report_hash_failures <arg>
whether to inform the user that hash failures occur.
They're non-fatal. (defaults to 0)


So for example:
btdownloadcurses.bittorrent --max_upload_rate 20 --minport 12345 --maxport 23456 file_name.torrent