Feedback-ID: i4779463d:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-757-gc3ad9c75d3-fm-20220722.001-gc3ad9c75
Mime-Version: 1.0
Message-Id: <2dcb598a-eac4-4fbf-8f38-a2b515331f8a@www.fastmail.com>
In-Reply-To: <3d864872-bc5c-40b0-9eab-2b38add2aa55@www.fastmail.com>
References: <3d864872-bc5c-40b0-9eab-2b38add2aa55@www.fastmail.com>
Date: Sat, 23 Jul 2022 06:00:22 -0700
From: "Anton Shevchenko" <anton@sancoder.com>
To: "Bitcoin Devs" <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain
Subject: Re: [bitcoin-dev] bitcoind -proxy=host:port doesn't work for
	unroutable	network
Precedence: list

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@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev