Is there a way NOT to connect to specific peers?

[DaveF]

I am doing some lightning builds and I am trying to have some nodes (bitcoin not lightning) NOT talk to each other.
Mostly I do not want the lower power RPis to connect to the other nodes on the network during sync.

I have tried addnode with remove and disconnect node, but they keep coming back.
They are all on the same private network so I don't know if that is causing the issue.

It's not really critical, but I figure I am just missing something simple.

Thanks,
Dave

[1714061639]

1714061639

[1714061639]

1714061639

[1714061639]

1714061639

[nc50lc]

Mostly I do not want the lower power RPis to connect to the other nodes on the network during sync.

Just make them connect to specific nodes instead of blocking them from your other nodes.
Add connect="node" (one line per node) to the RPis node's config file.
By using "connect", your node will not connect to other nodes other than the ones you listed.

[pooya87]

you can "ban" the nodes you don't want to connect to. that is basically the manual version of what bitcoin core automatically does for bad nodes. the command name that you should use is setban and the details of how to use it is as follows:

Code:

setban "subnet" "command" ( bantime absolute )

Attempts to add or remove an IP/Subnet from the banned list.

Arguments:
1. subnet      (string, required) The IP/Subnet (see getpeerinfo for nodes IP) with an optional netmask (default is /32 = single IP)
2. command     (string, required) 'add' to add an IP/Subnet to the list, 'remove' to remove an IP/Subnet from the list
3. bantime     (numeric, optional, default=0) time in seconds how long (or until when if [absolute] is set) the IP is banned (0 or empty means using the default time of 24h which can also be overwritten by the -bantime startup argument)
4. absolute    (boolean, optional, default=false) If set, the bantime must be an absolute timestamp in seconds since epoch (Jan 1 1970 GMT)

Examples:
> bitcoin-cli setban "192.168.0.6" "add" 86400
> bitcoin-cli setban "192.168.0.0/24" "add"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setban", "params": ["192.168.0.6", "add", 86400] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/

ref: https://bitcoincore.org/en/doc/0.19.0/rpc/network/setban/

[DaveF]

you can "ban" the nodes you don't want to connect to. that is basically the manual version of what bitcoin core automatically does for bad nodes. the command name that you should use is setban and the details of how to use it is as follows:

Code:

setban "subnet" "command" ( bantime absolute )

Attempts to add or remove an IP/Subnet from the banned list.

Arguments:
1. subnet      (string, required) The IP/Subnet (see getpeerinfo for nodes IP) with an optional netmask (default is /32 = single IP)
2. command     (string, required) 'add' to add an IP/Subnet to the list, 'remove' to remove an IP/Subnet from the list
3. bantime     (numeric, optional, default=0) time in seconds how long (or until when if [absolute] is set) the IP is banned (0 or empty means using the default time of 24h which can also be overwritten by the -bantime startup argument)
4. absolute    (boolean, optional, default=false) If set, the bantime must be an absolute timestamp in seconds since epoch (Jan 1 1970 GMT)

Examples:
> bitcoin-cli setban "192.168.0.6" "add" 86400
> bitcoin-cli setban "192.168.0.0/24" "add"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setban", "params": ["192.168.0.6", "add", 86400] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/

ref: https://bitcoincore.org/en/doc/0.19.0/rpc/network/setban/

So, this was working fine. Then a small oops.
Came in this AM to see how some things were syncing and instead of using the private IP they had looped in an out through the router.
Just had to ban the public IP.

Thanks,
Dave