📅 Original date posted:2022-07-23
📝 Original message:Sorry to post here. Now I realize this is an implementation issue.
Raised an issue at github - https://github.com/bitcoin/bitcoin/issues/25684
-- Anton Shevchenko
On Fri, Jul 22, 2022, at 10:08 PM, Anton Shevchenko via bitcoin-dev wrote:
> Hello,
>
> Got unexpected behavior when trying to run bitcoind with -proxy setting.
> -proxy is used to connect to SOCKS5 proxy which is able to access some
> internal network.
> bitcoind is started with -noconnect option and network activity is
> absent (as it should be).
>
> Then I command bitcoin-cli to connect to node with address 10.x.y.z
> with the command
> bitcoin-cli addnode 10.x.y.z add
>
> Expected behavior is for bitcoind to initiate connection through proxy.
> Actual behavior is bitcoind trying to connect without using proxy.
>
> In the code:
> CConnman::ConnectNode calls GetProxy and GetProxy returns false because
> CNetAddr::GetNetwork returns NET_UNROUTABLE.
>
> My take is this is unexpected behavior at minimum and should be documented.
> Better way is to introduce another option just for the unroutable addresses:
> - connect locally (for compatibility reasons, default);
> - connect thru proxy;
> - don't connect to unroutable addresses.
>
>
> -- Anton Shevchenko
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Anton Shevchenko [ARCHIVE] /
npub1s3…fs7ae
2023-06-07 23:12:08
in reply to nevent1q…xhrc
Author Public Key
npub1s30u622v6qh9zh88pmnr8ahv5cdxh6slu3rhqh57vzsrs8h8qehq0fs7aeSeen on
wss://relay.nostr.bandPublished at
2023-06-07 23:12:08Event JSON
{
"id": "fec0b3de8ed39317e41e43ce3195bd44502fbb6f71614a20e7c808721412059b",
"pubkey": "845fcd294cd02e515ce70ee633f6eca61a6bea1fe447705e9e60a0381ee7066e",
"created_at": 1686179528,
"kind": 1,
"tags": [
[
"e",
"e88f7b2748c53d42d6fa18a727fadd1ae7b8086e4f0576be824c18f37efca039",
"",
"root"
],
[
"e",
"efd94be962bfd31b75deca9dd8dfad134dc846cc0d884e1e6c8cd0bd46870c8c",
"",
"reply"
],
[
"p",
"845fcd294cd02e515ce70ee633f6eca61a6bea1fe447705e9e60a0381ee7066e"
]
],
"content": "📅 Original date posted:2022-07-23\n📝 Original message:Sorry to post here. Now I realize this is an implementation issue.\nRaised an issue at github - https://github.com/bitcoin/bitcoin/issues/25684\n\n-- Anton Shevchenko\n\nOn Fri, Jul 22, 2022, at 10:08 PM, Anton Shevchenko via bitcoin-dev wrote:\n\u003e Hello,\n\u003e\n\u003e Got unexpected behavior when trying to run bitcoind with -proxy setting.\n\u003e -proxy is used to connect to SOCKS5 proxy which is able to access some \n\u003e internal network.\n\u003e bitcoind is started with -noconnect option and network activity is \n\u003e absent (as it should be).\n\u003e\n\u003e Then I command bitcoin-cli to connect to node with address 10.x.y.z \n\u003e with the command\n\u003e bitcoin-cli addnode 10.x.y.z add\n\u003e\n\u003e Expected behavior is for bitcoind to initiate connection through proxy.\n\u003e Actual behavior is bitcoind trying to connect without using proxy.\n\u003e\n\u003e In the code:\n\u003e CConnman::ConnectNode calls GetProxy and GetProxy returns false because \n\u003e CNetAddr::GetNetwork returns NET_UNROUTABLE.\n\u003e\n\u003e My take is this is unexpected behavior at minimum and should be documented.\n\u003e Better way is to introduce another option just for the unroutable addresses:\n\u003e - connect locally (for compatibility reasons, default);\n\u003e - connect thru proxy;\n\u003e - don't connect to unroutable addresses.\n\u003e\n\u003e\n\u003e -- Anton Shevchenko\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "c4fbbd63269e49e8415a1bf2a9c256ba7822e800a7c61d17d13489660df2e2ed596cd6db3aff7ddbddbe0a257db273a393532b73dbf26ff8c543b8717c2dc5e4"
}