From: Wladimir <laanwj@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Anyone using bitcoind that needs RPC bound to interface? [testing needed]
Date: Mon, 31 Mar 2014 10:07:53 +0200 [thread overview]
Message-ID: <CA+s+GJDHBZVYdN_KWdLm9-dBa6mJb2y1=sqZ=nAeJbOjQXN_kg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
A while ago I created a patch to make it possible to bind the RPC port to a
specific address or even multiple address/port pairs.
https://github.com/bitcoin/bitcoin/pull/3695
I'm fairly confident that it works, but it cannot hurt if some people that
need this functionality tested it before merge. Test results from normal
setups as well as weird corner cases (IPv4+IPv6, VPNs, ...) are welcome.
Regards,
Wladimir
[-- Attachment #2: Type: text/html, Size: 583 bytes --]
reply other threads:[~2014-03-31 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJDHBZVYdN_KWdLm9-dBa6mJb2y1=sqZ=nAeJbOjQXN_kg@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox