Topic: Should we be using higher port numbers (IANA guidelines) (Read 514 times)
Cryptos have taken 8080 as well
Yes, I can see the logic in staking out the turf.
So if we're talking about a new p2pool for example, do you think above 49152 would be the best choice of port for pool connections or below?
Quote
49153 through 64000 for clonecoins
Hee hee - that should just about be enough space.So if we're talking about a new p2pool for example, do you think above 49152 would be the best choice of port for pool connections or below?
Yeah but every clonecoin and its clones and their clones and all the forks of all of those all want to be established so need to stake out their turf aka port-number, right?
So maybe we need a new range, 49153 through 64000 for clonecoins, that will still leave 64001 through 65535 for private stuff!
Someone contact IANA!
-MarkM-
So maybe we need a new range, 49153 through 64000 for clonecoins, that will still leave 64001 through 65535 for private stuff!
Someone contact IANA!
-MarkM-
I've just been reading some stuff about ports on http://www.speedguide.net/ports.php :
Just wondering if we should really be using higher port numbers (49152 to 65535) in our setups (new coins, etc)?
I'm posting this here in the altcoin forum as Bitcoin seems to be established on its port 8333.
Quote
The port numbers are divided into three ranges:
Well Known Ports: 0 through 1023
Registered Ports: 1024 through 49151
Dynamic (Private) Ports: 49152 through 65535
Well Known and Registered ports should not be used without IANA registration.
Well Known Ports: 0 through 1023
Registered Ports: 1024 through 49151
Dynamic (Private) Ports: 49152 through 65535
Well Known and Registered ports should not be used without IANA registration.
Just wondering if we should really be using higher port numbers (49152 to 65535) in our setups (new coins, etc)?
I'm posting this here in the altcoin forum as Bitcoin seems to be established on its port 8333.
Jump to: