vod Posted June 22, 2006 Report Share Posted June 22, 2006 Hi guys,previously i setup net.outgoing.port to use port 16384. now when i change net.outgoing.port back to the default value "0", i still see utorrent log reporting lots of requesting and sending from and to port 16384. i tried to change the port to other port beside default value of "0" (tried various ports, 12121, 13456, etc) but utorrent log still showing connection receive/send from/to port 16384. i have even remove all content of appsdata/utorrent, reinstall utorrent 1.5.1 (previously was using beta 464) but the problem still persist.the above happen to all torrents. i tried to add new torrent into utorrent, started it and watched the log. still, it used port 16384.partial logs from utorrent. to respect privacy, last 3 digits of IP address were masked intentionally----------------------------------------------51.156: 129.44.235.xxx : [bitComet/0101 ]: Sending Piece 949:16384->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Piece: 2422:163840->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Request: 482:180224->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Request: 482:196608->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Request: 482:212992->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Request: 482:229376->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Got Request: 482:245760->1638451.625: 196.202.75.xxx : [bitComet/0066 ]: Requesting 2664:0->1638451.640: 196.202.75.xxx : [bitComet/0066 ]: Sending Piece 482:180224->1638451.765: 129.44.235.xxx : [bitComet/0101 ]: Sending Piece 949:32768->1638452.125: 221.210.227.xxx : [bitComet/0063 ]: Got Request while choked: 2542:163840->1638452.156: 221.210.227.xxx : [bitComet/0063 ]: Got Request while choked: 2542:180224->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Request while choked: 2542:196608->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Request while choked: 2542:212992->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Request while choked: 2542:229376->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Cancel Unrequested: 2542:163840->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Cancel Unrequested: 2542:180224->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Cancel Unrequested: 2542:196608->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Cancel Unrequested: 2542:212992->1638452.171: 221.210.227.xxx : [bitComet/0063 ]: Got Cancel Unrequested: 2542:229376->1638452.375: 217.165.28.xxx : [bitComet/0057 ]: Got Unchoke52.406: 217.165.28.xxx : [bitComet/0057 ]: Requesting 1546:32768->1638452.421: 217.165.28.xxx : [bitComet/0057 ]: Requesting 1546:49152->16384-------------------------------------------------------any advise?thanks a lot Link to comment Share on other sites More sharing options...
schnurlos Posted June 22, 2006 Report Share Posted June 22, 2006 As we tested a lot (vod and I), it seems, that its equal which port we use at "net.outgoing_port", always port 16348 is used.Perhaps a bug in utorrent?PS: tested with 465or is this only working, when "net.outgoing_ip" is used? Link to comment Share on other sites More sharing options...
Switeck Posted June 22, 2006 Report Share Posted June 22, 2006 You typically have to restart µTorrent for it to accept port changes.Beyond that, the OTHER side (other peers+seeds) still thinks you're using the old port. So that's what they try to connect to you on. Link to comment Share on other sites More sharing options...
vod Posted June 22, 2006 Author Report Share Posted June 22, 2006 dont think so. i change the port to its default of "0". restarted utorrent. added a fresh new torrent. still the log shows the old port. P/S: the fresh newly added torrent should connect to new peers and seeds. none of them should know and/or think that i use port 12345 because there was simply no connection attempted yet. Link to comment Share on other sites More sharing options...
schnurlos Posted June 22, 2006 Report Share Posted June 22, 2006 Switeck1+ vod; this we tested a lot Link to comment Share on other sites More sharing options...
Firon Posted June 22, 2006 Report Share Posted June 22, 2006 Um. The log (and the Peer list) shows the remote port. net.outgoing_port has NOTHING to do with that. Link to comment Share on other sites More sharing options...
vod Posted June 23, 2006 Author Report Share Posted June 23, 2006 remote port? my remote port is set to 5060. the logs only shows incoming connection attempted by [peerIP] to port 5060 whenever there is incoming connection attempt. that only happen on initial establishment of connection. the rest of the logs shows lots of connection on port 16384 Link to comment Share on other sites More sharing options...
Ultima Posted June 23, 2006 Report Share Posted June 23, 2006 Huh? That 16384 in the log isn't even a port number O.oBesides that, YOU don't set the remote port. The remote user does -- hence the name. You've got it all mixed up here. You only set up the listening port, and outgoing port if you do so in the advanced options, both of which are local port options, NOT remote. Link to comment Share on other sites More sharing options...
schnurlos Posted June 23, 2006 Report Share Posted June 23, 2006 But what does this 16384 show? Link to comment Share on other sites More sharing options...
Switeck Posted June 23, 2006 Report Share Posted June 23, 2006 16384 is bytes, exactly 16 KiloBytes to be exact. That is the standard packet size used by the BitTorrent protocol, so you'll see it quite often. It often takes numerous 16 KB packets to make up 1 chunk of a torrent. Torrent chunks are typically 256 KB to 2 MB, and are the smallest piece of a torrent to get an individual hash. So until a whole chunk is received, that portion cannot be checked for accuracy.I too see nothing in that log snippet which shows the port used by µTorrent. Or even any port numbers for that matter. Link to comment Share on other sites More sharing options...
Firon Posted June 24, 2006 Report Share Posted June 24, 2006 Yeah, that's just data transfer. The only time the Logger even shows the remote port is when you're connecting. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.