| This article is a part of the Azureus User Guide.|
UPnP is short for Universal Plug and Play - it is a feature that works with some compatible routers to open the required ports automatically. If Azureus is crashing often, you should try to disable UPnP in the options!
Azureus needs to open a connection for the outside world, through a port in your router. Currently Azureus randomly selects a port at initial setup (in any case, do not use the port 6881 any more). Let us use port 55321.
We need to tell your router that all that arrives on port 55321 has to be directed to your machine. UPnP in Azureus can do that for you, unless:
- your router doesn't support UPnP. Some routers, even if they are compatible with UPnP, have problems with this. In that case you need to dive into your router's manual and look up port forwarding.
- someone else on your LAN is already using the port you want to use
- UPnP: Mapping 'Incoming Peer Data Port (TCP/55321)' failed
- UPnP: Mapping 'incoming peer data port (TCP/55321)' has been reserved by 192.168.0.50" - please select a different port. Choose another port in Options > Connection > Incoming TCP listen port and save.
If your ISP disconnects you every 24 hours so that you have to reconnect (like German Telekom/T-Online) you should not use UPnP but set up port forwarding yourself.
The Universal Plug and Play plugin produces various informative messages. By default these are all enabled. To disable them go to Tools > Options > Plugins and select the UPnP plugin. You can now configure the plugin as you required. To disable the popups you disable the 3 "report ..." checkboxes.
The informative messages are on by default so that users know that UPnP is in action.
Known router problems:
- ADSL 11g - early firmware versions (earlier than 2.05) don't support UPnP.
- WRT54G v4(/5?) - doesn't do UDP/TCP on same port properly - use different ports for the 'Incoming TCP Listen Port' and DDB. Also disable the UDP tracker protocol if needed. User has reported that with v5 a hard-reset of the router was needed to get things working.
- WAG354G - very slow at releasing port mappings on exit. This causes Azureus to appear to hang when quit for several minutes. Avoid this by configuring Azureus not to release on exit.
- DG834 - some earlier firmware versions have buggy UPnP implementations - try updating the firmware to see if that helps.
Reporting UPnP problems:
If you experience UPnP problems, then you should have a look at the log view for the UPnP plugin (Plugins > Log Views > UPnP). The information there will describe how Azureus has tried to set up the appropriate connections using UPnP. If you need some help understanding what the messages mean (when things aren't working), copy the text and post it to the Azureus forums.
If you are asked to get the full UPnP log, you can do this by going to the UPnP options, and enable the "Output full debug information to log" setting. Then restart Azureus - the full UPnP debug information will be printed in the UPnP log view. This setting is only available in v220.127.116.11 and later.
If you have an earlier version of Azureus which does not have this setting, then follow these steps:
- Enable logging in Azureus.
- Enable logging to file - choose to save the output somewhere that you'll remember.
- Deselect *everything* for Information, Warning and Error, *except* "plug".
- Close down Azureus.
- Delete any log file that already exists in the save file location.
- Start up Azureus.
- Wait until Azureus has reported UPnP problems.
- Take a copy of the log file saved on disk.
That will contain information about other plugins as well, but it will contain the full log information about everything the UPnP plugin has tried to do.
Read the Azureus FAQ