Quote from: johnwhitestar on Today at 02:09:15 PM

They are all up to date, but the majority of them are not on the standard ports, that's why maybe we have issues to connect to them.
Don't know whether it's the right thing to add the port in the slimcoin.conf specifically.

Those with standard ports are listening nodes which will show up when you add the node, otherwise adding the node makes no difference to the getpeerinfo result (that's also how you can tell). This is because if a node is configured to listen on a port different from the standard 41682, you have to add the ip address and the port in order for your client to treat it as a potential listening node (and potentially sync from it). Otherwise, only nodes listening on the standard port are checked by the clients for being listening nodes and those that aren't specified as such (via addnode) are assigned an arbitrary port.

F'rinstance, the IP address (144.76.64.49) of my old (should have been decommissioned months ago) Hetzner host is listed in the strDNSSeed array, the list of supposedly-stable peers that a fresh node consults first when syncing from zero. However, I'd turned off the Slimcoin node because I'm working towards decommissioning the host. In the interests of stabilising the network, I reinstalled the Slimcoin node and synced up to date from a few-days-ago chain snapshot "ip" : "144.76.64.49" "blocks" : 2362979 with the (additional to the hardcoded strDNSSeed nodes) addnode=185.150.190.19:41682 and addnode=185.68.67.37:41682.

My client on the new server (144.76.118.44) sees the newly-started client on the old server as "inbound: true" and has assigned it a random port because I haven't told it otherwise (via addnode)

Code:

{
"addr" : "144.76.64.49:37520",
"services" : "00000001",
"lastsend" : 1614350096,
"lastrecv" : 1614350096,
"conntime" : 1614346618,
"version" : 60003,
"subver" : "/Satoshi:0.6.6/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f2-dirty-alpha)/",
"inbound" : true,
"releasetime" : 0,
"height" : 2361253,
"banscore" : 0
},

Also note that the blocks field of getpeerinfo is incorrect and unreliable , it reported the block height incorrectly as 2361253 and not 2362979.

I then logged on to the new server and executed addnode 144.76.64.49, then getpeerinfo with the result:

Code:

{
"addr" : "144.76.64.49:41682",
"services" : "00000001",
"lastsend" : 1614350497,
"lastrecv" : 1614350498,
"conntime" : 1614350497,
"version" : 60003,
"subver" : "/Satoshi:0.6.6/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f2-dirty-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 2362981,
"banscore" : 0
}

The addnode command caused the node to re-check, changing the port, updating the send/conn times changin the "Inbound" status and updating the "blocks" value to the correct one.

Right now, nodes worth adding are the listening nodes: 185.150.190.19, 185.68.67.37, 144.76.64.49, 144.76.118.44

And, just for comparison with before in terms of chain movement:

Code:

"addr" : "185.150.190.19:41682", "height" : 2362598,
"addr" : "185.68.67.37:41682", "height" : 2364101,
"addr" : "178.223.55.155:53184", "height" : 2363828,
"addr" : "178.223.55.155:56231", "height" : 2363843,
"addr" : "185.79.5.221:53014", "height" : 2363717,
"addr" : "145.239.189.106:53042", "height" : 2363845,
"addr" : "178.221.183.154:9715", "height" : 2363767,
"addr" : "178.221.183.154:9964", "height" : 2363720,
"addr" : "46.0.192.98:60366", "height" : 2362598,
"addr" : "178.223.55.155:64890", "height" : 2363689,
"addr" : "178.223.55.155:64902", "height" : 2363689,
"addr" : "94.25.174.181:39989", "height" : 2363729,
"addr" : "18.191.168.158:61845", "height" : 2287922,
"addr" : "144.76.64.49:37520", "height" : 2361253,
"addr" : "109.10.108.52:56155", "height" : 1340151,
"addr" : "94.25.174.181:33980", "height" : 2362964,
"addr" : "109.10.108.52:56698", "height" : 2362227,
"addr" : "5.39.70.87:47790", "height" : 2362979,

Cheers

Graham