1.How do I run Azureus on Linux?
To get Azureus to start on linux you need to download SWT.
Make sure you choose the right version, GTK or Motif (cf. PS).
Extract the contents of the zip file somewhere, then move all .jar files and .so files to the same directory as Azureus.jar.
Then run it with the following command line:
java -cp swt.jar:Azureus2.jar -Djava.library.path=. org.gudy.azureus2.ui.swt.Main
If you extracted SWT to another directory, change the paths in the command line accordingly.
If you would rather use .tar.gz2, it’s this way : Azureus for Linux.
PS: are you experiencing GUI freezes? If you are running Azureus from eclipse, try without it. If not, try with SWT-Motif instead of GTK.
And don’t forget the HOW TO guide…
2. I want to translate Azureus in my language…
3. What are the numbers in brackets?
The first number is the number of peers you are currently connected to.
The number in brackets is the number of peers seen by the tracker, that is the total number of peers in the swarm.
Works with seeds as well.
4. I have begun a download with another client…
* If it’s with a BitTorrent client working on versions prior to 3.3, you can safely resume your download with Azureus.
* From 3.3 on, you need to make your client, either pre-allocate the space used by the files or try and finish the allocation. If it can’t, it’s not safe to resume the download with Azureus.
* To continue downloads begun with BitComet, you need to check "Truncate existing files that are too large" in Options > Files as BitComet adds bytes at the end of the files…
5. What’s up with memory usage and CPU load?
* Memory usage is known to climb up and drop back repeatedly when using java jre 1.4.2 with some configurations. The cpu load is higher too.
Please use latest Java 1.5.
* A high CPU load has been experienced with some configurations using Zonealarm.
6. How can I limit my download speed?
From 184.108.40.206 on, Azureus has a built-in download speed limiter, available through configuration > transfer or by right-clicking on the download speed in the bottom status bar.
Some other programs however are also available:
* Netlimiter for windows users (Note: can cause 100% cpu usage on some configurations).
* The Wonder Shaper (or Trickle) for linux (openbsd, solaris…) users.
7. Ok, what’s with the IRC client?
Some might, and rightfully so, question the presence of an IRC client, although reduced to its simplest, into Azureus.
That requires a few words:
* you don’t have to use it, of course,
* it’s meant to be a gathering of experiences on the program, an exchange of thoughts, preferences, wishes even,
and most importantly,
* it took no time to implement it, so the main concern among Azureus’ team is still and always taking care of the development of the program itself.
8. How many torrents can be active or downloading at a time?
Azureus gives you 2 settings:
* Max active torrents: maximum number of torrents that are either "downloading", "seeding" or "ready".
* Max simultaneous downloads: maximum number of torrents "downloading".
(always inferior to (Highest port number – Lowest port number) and to (Max active torrents))
For instance, you have 4 torrents in Azureus. You set max active torrents to 3 and max simultaneous downloads to 2.
* You will then have 2 "downloading" torrents, and 1 torrent "ready" and 1 torrent "stopped".
When one download finishes, the torrent then switches to "seeding" mode and the "ready" torrent begins to download.
Once over, you will have 3 "seeding" torrents and a "stopped" one.
9. What is snubbed?
It’s what happens to a peer when he doesn’t send you the data he told you he would send.
You don’t trust him anymore so you ask him less pieces.
Go there for details.
10. How come my download speed is so slow?
First thing to check is your upload limit setting: if you use all your upload bandwidth, your download performance will be greatly impaired.
So be sure and check your line speed.
Run the configuration wizard (introduced in version 220.127.116.11), available from the File menu.
If you want to set some limits manually, please read the following:
Concerning your computer:
* Are you behind a router? Enable port forwarding to your computer on port 6881 (or whatever you specified in the configuration).
* how many peers are you connected to? Set "number of max connections per torrent" sufficiently high (to 100 for instance) in "configuration" menu > transfer, unless you have some disconnection issues.
* what’s the "total speed" of your torrent (directly under "max uploads" in the general view) ?
this gives you an estimate of the speed of your swarm, so an estimate of your speed (speed of the swarm/numbers of peers you’re connected to)
* When allocating bandwith, please allow at the very least 2kB/s per uploads (4kB/s is recommended), that means that using the default value of 4 uploads per torrent, you need AT LEAST 8kB/s of upload per downloading torrents. Not uploading will result in poor performances, trying to increase the number of uploads while the bandwidth is limited WILL result in a serious slow down.
My line is 512/128.
The settings for a BitTorrent application is directly linked to my max upload speed, here 128kbps (16kB/s).
So my max upload speed in azureus will be 13kB/s (letting room for download and browsing).
With 13kB/s upload, I can have 6 uploads at a time, because one upload needs to be at the very least least 2kB/s (uploading less might be damaging both for you and for the peer you’re uploading to – seeing that you’re not sending fast enough, the peer will ask someone else for the same piece and discard yours when it finally arrives, having downloaded it (and you uploaded it) for nothing… ).
I will have 2 active torrents (1 at most downloading, the other seeding) with 3 uploads each. (3 uploads means I will be uploading to 3 peers at a time on one torrent).
That way, if I’m only downloading, each peer will get 13/3 = 4kB/s approx, which is good and will make them sending me data more likely. The more you upload to a peer, the more likely he is to send you data fast.
And if I’m seeding one torrent and downloading another, each peer will get 13/6 = 2kB/s approx, which is ok.
All those settings should have been taken care of when you first ran the config wizard. Of course, it’s essential that you know your max upload speed for the wizard to be effective, both for the peers and for you.
11. What are "discarded" and "hash fails"?
Both represent amounts of data downloaded but not used.
* Discarded: is the data you somehow received although you didn’t need it, so you got rid of it.
Measured in chunks of 16KB (that Azureus uses).
* Hash fails: are pieces that failed the test of "validation", some wrong data was received, thus unusable.
Measured in pieces (whose size depends on the torrent). There is no normal amount of "hash fails" as it depends on peers sending wrong data.
12. What about IP Filtering?
For different reasons, you may want to prevent access to your computer to certain lists of IPs.
The IP filtering section helps you configure this.
You can get the safepeer plugin to automatically load Peer Guardian’s list of IPs.
13. What is "Incremental file creation"?
Incremental File Creation: only stores the file size. Allocation occurs as the files are downloaded. Results in a much more fragmented file.
14. What is torrent import/export?
* A torrent file contains information encoded using a space-efficient technique, however this renders the file hard to understand and modify. The "export torrent" facility allows this torrent information to be saved in an XML format which is more amenable to modification.
* The "import torrent" function takes an XML encoded torrent file and converts this back into the original format, making it usable as the basis for downloading/seeding.
* To uniquely identify a torrent a "hash" is computed from the "INFO" part of the XML document. For example, this hash is used when communicating with a tracker. Changes made to the "INFO" data will alter the hash value and make the torrent incompatible with other downloaders/seeders for the torrent content.
* The XML schema for XML torrent documents can be found here.
* Due to character set issues the torrent name and file name components are currently exported as hex encoded bytes.
15. What about XP skin?
You can add XP skin to Azureus thanks to this file to put in your jre/bin directory (and/or windows/system32 if it doesn’t work).
Original eclipse page.
16. Where can I find Plugins for Azureus?
17. What is the Embedded Tracker?
Azureus has a built in tracker to allow users to share torrents directly, rather than uploading them to an "external" tracker. This is called "hosting" and can be performed by selecting this option from the context menu on the "My Torrents" view.
Configure the details of the embedded tracker via the "Tracker" tab on the "Configuration" view. There is an "External tracker IP address" field that must refer to the external IP address of your machine. Note that if you are behind a firewall this may differ from your machine’s local address. To help in this task there is a "Check Address" button here. If your machine’s external address isn’t fixed (e.g. your ISP regularly changes it) then this will interfere with your hosted torrents, as the "announce url" will need to keep changing. If this is the case then it is advisable to use a DNS redirection service, such as DynDNS.org, to assign yourself a fixed DNS name – refer to the site for details.
In order to host a torrent it must have the correct "announce url" defined in the torrent. It must refer to the url of the embedded tracker. Use the File Menu/ "create a torrent" facility to construct a torrent, selecting the "Use Azureus embedded tracker" option to ensure the correct announce url is used. Then open the torrent and select "host". You will probably want to seed the new torrent, at least initially, so start the torrent and navigate to the file/directory used to create the torrent when selecting the download location.
You will see on the tracker configuration dialog that there is a port associated with the tracker, default value 6969. If you have a router/firewall you will need to open this port up for incoming TCP connections, as you will have done for the peer transport ports (default 6881 to 6889).
The tracker also, if enabled, publishes the hosted torrents and statistics as a web page. This can be accessed by using the tracker’s root url. For example, http://127.0.0.1:6969/. Other users can then download the torrents directly from here ( http://yourexternalIP:6969/ ).
18. What is "Publishing" a torrent?
The "My Torrent" context menu item "Publish" enables you to publish a torrent to the tracker’s web page (above) without hosting it. This provides a quick way of sharing a torrent with other users. The torrent’s existing tracker will be used by any other users, not yours.
19. Tracker Security (Passwords and SSL)…
Access to the tracker web pages and the tracker announce process can be controlled by password settings specified on the Tracker configuration panel. This supports basic authentication and as such the user name and password values are transmitted in plain text. This can further be protected by using SSL (below). Note that password protecting the tracker announce process requires a BitTorrent client capable of handling authentication, such as Azureus.
Communication with the tracker can be encrypted using SSL, again this requires a suitable client such as Azureus.
Configuration of SSL is required for both the Azureus downloader and tracker:
Tracker configuration: It is necessary to generate a public/private key pair for the SSL framework and store this in a file called ".keystore" located in Azureus’s home directory (where it stores the "azureus.config" file). It currently must have a keystore and key password of "changeit". Such a key pair can be generated via the following Java command ("keytool" can be found in the JRE bin directory).
* keytool -genkey -keystore %home%\.keystore -keypass changeit -storepass changeit -keyalg rsa -alias azureus
Various questions are asked during the key generation process. The important one is the first one, "What is your first and last name?" Respond to this with the dns name (or IP address) of the tracker.
The certificate required for clients can then be exported via
* keytool -export -keystore %home%\.keystore -keypass changeit -storepass changeit -alias azureus -file azureus.cer
Note that it is the certificate, NOT the private key that is distributed for client use. Also note that it is possible to directly obtain the certificate from the SSL protected tracker if using Internet Explorer, as it allows you to save the certificate when contacting the site.
Downloader configuration: The client must trust the certificate in order to communicate with the site. The certificate must be imported on the client into a certificate store called ".certs" in the same place as ".keystore" above. The command to do this is:
* keytool -import -keystore %home%\.certs -alias azureus -file azureus.cer
assuming the certificate is in file "azureus.cer". Again the password must be "changeit". When prompted say "yes" to "do you trust this certificate".
A good way to test that the tracker and downloader setup is going to work is to seed a torrent on the SSL tracker. Note that this requires Azureus to be set up as both Tracker and downloader above, and hence the ".keystore" and ".certs" files must both be populated via the three steps of key generation, certificate export and certificate import.
When creating a torrent to host using SSL, check the SSL checkbox on the "create torrent" wizard. This ensures that the announce url starts with "https" (as opposed to "http") and also that the SSL port number is used (as opposed to the non-SSL port, again see the Tracker configuration).
20. Installing and configuring the web access of the Azureus statistics…
* a web server of some kind installed on the Azureus PC (e.g. : Apache)
* an access to a Cocoon server (e.g. : http://www.mycgiserver.com), or
* a Cocoon server installed on the Azureus PC (http://xml.apache.org/cocoon/)
* Azureus ;o)
Steps to install:
1. Configure Azureus to make it output the Azureus_Stats.xml somewhere on your harddisk
2. (optional) Register for a Dyndns account (http://www.dyndns.org) and install a dyndns client updater (same URL)
3. Configure the http server so the Azureus_Stats.xml is published on the web (let’s say the URL will be http://my.server.org/azureus/Azureus_stats.xml)
4. Edit the azureus.cocoon.xml file, and replace the string http://xxx.homedns.org/azureus/Azureus_Stats.xml" with the URL you configured at step 3 (e.g. http://my.server.org/azureus/Azureus_stats.xml)
* Configure Cocoon so it publishes azureus.cocoon.xml and azureus.xsl, or
* Upload the azureus.cocoon.xml and azureus.xsl files to your MyCgiServer account
If you used a MyCgiServer account, and uploaded the files to a "/azureus" directory, you simply need to use the http://www.mycgiserver.com/~<account_name>/azureus/azureus.cocoon.xml URL to access your stats…
The azureus.xsl template is _very_ basic, feel free to update it with features and eye-candy!
21. What’s this "Health Indicator"?
The health indicator is an evaluation of how well your torrent is going.
means that your torrent is stopped,
means that you’re not connected to any peer,
when seeding, it means that you’re not yet connected to any peer,
when downloading, it means that you are connected to some peers but the tracker is down,
means that the tracker is ok, you’re connected to peers, but you don’t have any remote connection. You may have a NAT problem if your torrents stay on yellow status all the time,
means that everything is going fine.
"peers" means both peers and seeds here.
22. What’s this "Super Seeding"?
Super Seeding is a special optimised seeding mode.
Only use this mode when you are the first and only seeder.
Each peer will be assigned a piece, and Azureus will then compute the time it takes for that particular piece to be seen again the swarm, thus identifying peers with high upload speed, to which Azureus will preferentially give data.
The additional information is available in the details view, right-click "Choose the columns to display".
23. What about the incoming ports?
From 18.104.22.168 on, you can use a single port for all your torrents.
You previously had to adjust the number of ports used, opened or forwarded to the number of running torrents.
Now, only one port is necessary, no matter how many active torrents there are.
24. Weird systray display ?
Please update your systray4j.dll, to place in your Azureus directory.
25. 22.214.171.124 : where are my plugins ?
The plugins can now be found in the directory specified in your configuration tab (depending on your system: Win: C:\Documents and Settings\username\Application Data\Azureus\, OSX: /Users/username/Library/Azureus/, Linux: /home/username/Azureus/).
Any new plugin will have to be placed in that directory in its own directory.
26. How can I display my torrents on my webpage?
You can use a little php script available here. Be sure and read the HowTo.