MoonPoint Support Logo

 




Advanced Search
←November→
Sun Mon Tue Wed Thu Fri Sat
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
←2026→
Months
NovDec


Sun, Nov 01, 2026 6:18 pm

Deluge's location for the incoming port number on Windows systems

When Deluge is run on a system running the Microsoft Windows operating system, it stores the location it uses for the incoming port number(s) in a configuration file, core.conf under the user's %APPDATA%\deluge directory. The %APPDATA% environment variable usually expands to something like the following, where YourUserName is the user name for the relevant Windows account:

C:\Users\YourUsername\AppData\Roaming\deluge\core.conf

Note: You can see the value for %APPDATA% by issuing the command echo %APPDATA% in a command prompt window. The %APPDATA% directory is a hidden directory, but you can see the contents of the Deluge configuration directory in the Windows file manager even if you haven't turned on the display of hidden folders by putting %APPDATA%\deluge in the address field in the file manager. You can then right-click on the file and choose to open it with the Windows Notepad. You can also access the directory by pressing the Win + R keys.

By default, Deluge uses a random network port or the 6881-6889 range (frequently defaulting to 6881 in many setups like Docker). You can check or change the exact active incoming port when Deluge is running under Preferences → Network. If you open the configuration file in a text editor, such as Windows Notepad, you will see something similar to the following:

"listen_ports": [6881, 6891], "random_port": false

If you need to change the port before starting Deluge, e.g., to match an incoming port provided by a VPN provider, you can change the values. E.g., if you wanted Deluge to use port 39755, you could put the following entries in the file and then start Deluge:

    "listen_ports": [
        39755,
        39755
    ],
    "listen_random_port": null,
    "listen_reuse_port": true,

Note: If you need the actual port Deluge is listening on right now, rather than its saved setting, check Deluge's Preferences → Network → Incoming Ports. With random port selection enabled, the active port can differ from the saved value if you haven't restarted Deluge after updating the port number.

When you start Deluge, you can see if there are incoming connections to that port using the netstat command. E.g., netstat -an | find "39755".

C:\Users\Jill>netstat -an | find "39755"
  TCP    10.164.7.152:39755     0.0.0.0:0              LISTENING
  TCP    10.164.7.152:39755     10.43.22.249:64621     TIME_WAIT
  TCP    10.164.7.152:39755     10.157.104.168:49659   TIME_WAIT
  TCP    10.164.7.152:39755     10.157.104.168:57171   TIME_WAIT
  TCP    10.164.7.152:39755     10.169.234.135:49738   TIME_WAIT
  TCP    10.164.7.152:39755     10.169.234.135:55102   TIME_WAIT
  TCP    10.164.7.152:39755     10.175.210.63:50713    TIME_WAIT
  TCP    10.164.7.152:39755     10.194.155.52:14534    SYN_RECEIVED
  TCP    10.164.7.152:54686     178.93.201.240:39755   SYN_SENT
  TCP    127.0.0.1:39755        0.0.0.0:0              LISTENING
  TCP    192.168.1.7:39755      0.0.0.0:0              LISTENING
  UDP    10.162.7.159:39755     *:*
  UDP    127.0.0.1:39755        *:*
  UDP    192.168.1.7:39755      *:*

C:\Users\Jill>

References:

  1. Deluge FAQ
    Deluge
  2. Deluge User Guide
    Deluge

[/network/p2p] permanent link

Wed, Nov 23, 2016 10:20 pm

Streaming video to a DLNA device with Vuze

Vuze is a BitTorrent client that can also be used to stream audio and video to a Digital Living Network Alliance (DLNA) device over a network connection. The software is free, but you do need to be careful when installing the software to select the "customize" option to ensure that third-party software bundled with Vuze is not installed with Vuze, since that third-party software may be adware. E.g., see Avoiding the installation of adware when installing Vuze and Vuze - Select customize option to avoid adware/malware during upgrade. E.g., I found GeniusBox software installed on a system during the installation of Vuze when that third-party software was bundled with Vuze. But, as long as you select the "customize" option and decline all third-party software that may be bundled with Vuze, you should be ok.

DLNA provides a standard for sharing digital media among multimedia devices and Vuze can be used to stream audio and video from a computer to a device that supports the DLNA standard, e.g., a input device for a television (TV).

[ More Info ]

[/network/p2p/vuze] permanent link

Fri, Nov 21, 2008 5:27 pm

DC++ Shared File Locations

DC++, a Peer to Peer (P2P) filesharing program, stores settings in DCPlusPlus.xml, which you will find in the directory where it is installed. You will find the locations of shared files between share tags. The following is an example.


       <Share>
		<Directory Virtual="Comics & Etc">S:\Comics & Etc\</Directory>
		<Directory Virtual="Cartoons">T:\Cartoons\</Directory>
		<Directory Virtual="Books">T:\Books\</Directory>
	</Share>

[/network/p2p] permanent link

Thu, May 15, 2008 11:00 pm

Comcast and Cox Continue to Block BitTorrent Traffic

A report by Germany's Max Planck Institute reveals that Comcast and Cox Communications are blocking BitTorrent traffic throughout the day, despite Comcast's claims that it only throttles BitTorrent Traffic during peak network hours. Comcast also claims that its throttling of BitTorrent traffic is imperceptible to its customers. It is likely true that most of Comcast's customers won't realize that degraded performance for BitTorrent transfers are occurring because Comcast is actively throttling that traffic.

References:

  1. Cox, Comcast Accused of More BitTorrent Blocking
    By Roy Mark
    May 15, 2008
    eWeek.com

[/network/p2p] permanent link

Sun, Dec 30, 2007 11:12 pm

LimeWire

After I had cleaned a lot of malware from someone's home system, I found LimeWire on the system. McAfee security software was on the system and prompted me as to whether I wanted to allow LimeWire to run or block it. My last experience with LimeWire was several years ago. At that time I had found the free version came bundled with adware/spyware, so I had the McAfee software block LimeWire. After checking on the current version, though, I found it no longer comes bundled with adware/spyware according to the developer, Lime Wire LLC (see LimeWire's response: Spyware) and the Wikipedia article on LimeWire.

Granted, one should never rely on the developer's or distributors' word on such matters, since they will often simply define the terms "adware" and "spyware" so that they don't include techniques used by their software, instead of using the commonly accepted definitions. But, as far as I can determine, LimeWire has indeed been distributed, even in the free version, without adware or spyware for several years now.

[ More Info ]

[/network/p2p] permanent link

Valid HTML 4.01 Transitional

Privacy Policy   Contact

Blosxom logo