Topic: Consiquence of changing default listening port. (Read 1371 times)
Yes it does matter. I get less connections when the default port was changed.
Then that's stupid to prefer a port when it was designed to be broadcast
I doubt it but it could be because my nmc doesn't get incoming and I'm using a different port than stock
If you're not getting incoming, you're effectively not using that port.
I doubt it but it could be because my nmc doesn't get incoming and I'm using a different port than stock
Yes, you are able to change the listening port, and yes, if you change the listening port you will advertise your address along with the new port. However, unless I'm misremembering, the default behavior of Bitcoin Core is to prefer connections on port 8333, so you're unlikely to get many (if any) incoming connections.
OMG. That's bad. Anyone else confirming this?
Yes, you are able to change the listening port, and yes, if you change the listening port you will advertise your address along with the new port. However, unless I'm misremembering, the default behavior of Bitcoin Core is to prefer connections on port 8333, so you're unlikely to get many (if any) incoming connections.
Just to confirm, suppose I change the default listening port for bitcoind/-qt which's intended for incoming connection from other wallets, I will get the same no. of connections as with the default port right?
OR the question can be framed as --
Is the Bitcoin protocol hard coded for port 8333, or will it get the open port from the running wallet and forward it to other clients so they can connect to the right port?
OR the question can be framed as --
Is the Bitcoin protocol hard coded for port 8333, or will it get the open port from the running wallet and forward it to other clients so they can connect to the right port?
Jump to: