Page 1 of 1
UPnP port 4433
Posted: Wed Aug 22, 2012 12:26 am
by basl
Hey guys,
So I used my default torrent port 60000 as the listening port for incoming connections.
Everything looks fine. I also enabled upnp.
But when I look in my router(dd-wrt) I see an extra port, port 4433.
The two ports open when I open qB on my pc. These are 60000 tcp, 60000 udp and 4433 tcp (check the included logs from qB and dd-wrt(router))
I don't see this port anywhere mentioned in the configuration or even the conf file.
The port isn't mentioned anywhere on the forums and a google search doesn't answer the question either.
Can anyone tell me why this port is being opened on my router, without my consent?
Thx in advance.
Code: Select all
Forwards
Description Enabled From (WAN) To (LAN) IP Address Protocol
qBittorrent v3.0.0 at ***.***.***.***:60000 Yes 60000 60000 ***.***.***.*** TCP
qBittorrent v3.0.0 at ***.***.***.***:4433 Yes 4433 4433 ***.***.***.*** TCP
qBittorrent v3.0.0 at ***.***.***.***:60000 Yes 60000 60000 ***.***.***.*** UDP
Code: Select all
22/08/2012 02:02:29 - Peer ID: -qB3000-
22/08/2012 02:02:30 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 60000
22/08/2012 02:02:30 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 4433
22/08/2012 02:02:30 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 60000
22/08/2012 02:02:29 - Options were saved successfully.
22/08/2012 02:02:29 - Embedded Tracker [OFF]
22/08/2012 02:02:29 - Encryption support [ON]
22/08/2012 02:02:29 - Local Peer Discovery support [ON]
22/08/2012 02:02:29 - PeX support [ON]
22/08/2012 02:02:29 - DHT support [ON], port: UDP/60000
22/08/2012 02:02:29 - HTTP user agent is qBittorrent v3.0.0
22/08/2012 02:02:29 - UPnP / NAT-PMP support [ON]
22/08/2012 02:02:29 - qBittorrent is bound to port: TCP/60000
Re: UPnP port 4433
Posted: Wed Aug 22, 2012 5:14 am
by Tomaso
Could it be the "Check for software updates" function that uses this port?
Re: UPnP port 4433
Posted: Wed Aug 22, 2012 6:56 am
by Dayman
This port is used for ssl torrents.
From libtorrent documentation:
ssl_listen sets the listen port for SSL connections. If this is set to 0, no SSL listen port is opened. Otherwise a socket is opened on this port. This setting is only taken into account when opening the regular listen port, and won't re-open the listen socket simply by changing this setting.
It defaults to port 4433.
There is no option to control this port in qBittorrent unfortunately.
Re: UPnP port 4433
Posted: Wed Aug 22, 2012 2:21 pm
by basl
Thx for your guys' responses.
So from what I understand, is that this listening port is used for enabling SSL torrents. (in combination with openssl, which I don't see anywhere mentioned in qB).
A feature from the libtorrent platform, that is enabled in qB as a default setting.
Maybe it's an idea to propose a new feature in qB which enables you to turn this off.
If I should believe the sentence below from the manual, it shouldnt be hard for the devs.
Code: Select all
To not listen on an SSL socket at all, set ssl_listen to 0.
Thx.
Re: UPnP port 4433
Posted: Wed Aug 22, 2012 2:51 pm
by Dayman
http://www.rasterbar.com/libtorrent_blo ... -over-ssl/
Interesting. I've never seen any SSL-enabled torrents with embedded certs.
Re: UPnP port 4433
Posted: Wed Aug 22, 2012 11:29 pm
by basl
Guess I will switch to port 4433 for my torrenting.
Better one, then two ports open.
Torrenting over ssl seems to be the way to go in the future.
Trackerless bittorrenting with encrypted traffic.
May be an idea for Demonoid v2.
Re: UPnP port 4433
Posted: Wed Jan 16, 2013 5:12 pm
by christophe.dumez
qBittorrent v3.0.7 will no longer listen on port 4433. I have disabled it for now since we do not technically support SSL torrents at this point.
Re: UPnP port 4433
Posted: Sun May 04, 2014 1:29 pm
by stoatwblr
3.1.9 is listening on this port too.
No idea if this is intentional but I feel it's worthwhile tacking the update onto this thread in case anyone's googling for the port (as I was), especially in light of the recent heartbleed issues (update to 3.1.9.2!)
Re: UPnP port 4433
Posted: Sun May 04, 2014 1:34 pm
by sledgehammer_999
This port is used for SSL torrents which are disabled in qbt.
Are you sure you don't have setup your WebUI port to that (or you bittorrent/dht port to that)?
Re: UPnP port 4433
Posted: Sun May 04, 2014 1:43 pm
by stoatwblr
Quite sure. WebUI is 8080 and the other ports are all up around 56000. I spotted it being opened in logs and went looking to find out what it's for.
*** starting log ***
00:00:00.005 done starting session
00:00:00.006 listening on: 0.0.0.0:56882 external port: 56882
00:00:00.006 listening on: 0.0.0.0:4433 external port: 4433
00:00:00.006 listening on: [::]:56882 external port: 56882
00:00:00.006 failed to bind to interface "[::]:4433": Address already in use
00:00:00.006 listening on: [::]:4434 external port: 4434
Re: UPnP port 4433
Posted: Sun May 04, 2014 1:51 pm
by stoatwblr
FWIW: It's not there in 3.1.9.2 (just updated)
Re: UPnP port 4433
Posted: Sun May 04, 2014 1:56 pm
by sledgehammer_999
Oh come on, were you really using a version older than 3.0.7 and came here to complain about port 4433 even though you saw that this was supposed to be disabled in 3.0.7 onwards?
EDIT: Sorry, you mention that you used 3.1.9. This is odd, it should be happening with 3.1.9 ...
Re: UPnP port 4433
Posted: Sun May 04, 2014 2:23 pm
by ciaobaby
00:00:00.006 failed to bind to interface "[::]:4433": Address already in use
Which means some other application on your machine is already using 4433
Re: UPnP port 4433
Posted: Sun May 04, 2014 4:10 pm
by stoatwblr
ciaobaby wrote:
00:00:00.006 failed to bind to interface "[::]:4433": Address already in use
Which means some other application on your machine is already using 4433
I know what it means. but it also means that qbittorrent tried to bind to the port (and no, lsof + netstat showed nothing binding to that port in ipv6)
Re: UPnP port 4433
Posted: Sun May 04, 2014 4:33 pm
by sledgehammer_999
No need to continue this. This is an old thread. The bug apparently doesn't show up in 3.1.9.2. If it somehow, shows up again please reply here or open a new thread.