Whitelisting works for subnets for outgoing and incoming connections, unless the node has been added using addnode, in which case the permissions are always "N/A" in the GUI and the node is disconnected as if there is no whitelisting (e.g. when historical block download is reached, or a mempool request comes in, etc).
whitelisting fails for nodes added with addnode #26464
issue rebroad opened this issue on November 6, 2022-
rebroad commented at 4:02 PM on November 6, 2022: contributor
- rebroad added the label Bug on Nov 6, 2022
-
jonatack commented at 4:18 PM on November 6, 2022: contributor
Regarding the GUI showing permissions of "N/A" when getpeerinfo returns
"permissions": []you may want to review https://github.com/bitcoin-core/gui/pull/677, in which the last commit proposes to change "N/A" to "None". -
- rebroad closed this on Dec 10, 2022
- rebroad closed this on Dec 10, 2022
- bitcoin locked this on Dec 10, 2023
