connecting to peers

[Jet Cash]

As some of you guys know, I run a full node over public WiFi. It's not always on, but I connect two or three times every day. Inbound connectins are blocked by the service provider, but I used to be able to find eight connections fairly quickly. Over the last month or so, I've noticed that it is taking some time to find peers, and sometimes only four or five are listed. Those that are found seem to be high quality ( sub 100ms), and previously speeds could be over 3000ms. I'm still on 0.14.1 as I decided to wit until after the forking had died down before upgrading.

My question is - Am I being avoided for some reason? I can think of a few reasons -

• I'm running a part time node
• I'm still on 0.14.1
• Political pressure means that I should decide to support one of the forks
• I have a low grade internet connection

[1715495411]

1715495411

[1715495411]

1715495411

[1715495411]

1715495411

[Jet Cash]

I've crept up to 8 peers with fast connections, so I have no problems keeping up to date at the moment. Having read the other thread about nodes and segwit. I'm now concerned that there may be attempts to force me to upgrade to core versions with large blocksizes, so I'm considering reviving my old Ubuntu core to increase the number of legacy nodes.

[ScripterRon]

You should check the log for your node (debug.log in the Bitcoin data directory).  See if connection attempts are being rejected or dropped.  I run a 24/7 0.15 node on my VPS and I see a number of 0.14 inbound connections, so that shouldn't be the problem.

As an aside, I currently have 100 connections and none of them identify themselves as S2X nodes.  I'm not rejecting S2X connections (I modified 0.15 to only reject BitcoinABC connections), so that isn't the issue.  When the fork happens in mid-November, it looks like the bulk of the user nodes will not follow the new chain but stay on the current chain (including my node).  Unless the S2X nodes are in deep stealth mode and identify themselves as Bitcoin Core 0.15

[btctousd81]

maybe you are getting banned by network nodes, for relaying bad tx to often.,

have you whitelisted any node which relays bad txs ?

try checking your debug.log file's last 200 lines.,

you will see what is happeing .,

• I'm running a part time node

nope
it does not matter , if you keep your bitcoin-core on for few minutes or few hours. this doesnt qualify for increasing banscore.,

• I'm still on 0.14.1

nope, doesnt matter.

• Political pressure means that I should decide to support one of the forks

i am not sure, what that means.

• I have a low grade internet connection

doesnt matter, as long as you are connect to internet.


try adding this line in your bitcoin.conf

Code:

forcednsseed=1

this line will make sure to get fresh new nodes, when you start your bitcoin-core from builtin nodes list.