[PATCH REQUEST] Variable ports (205BTC reward)
(I am poor)
Bitcoin donations received: 344.29
You probably didn’t need to claim poverty.
If someone wrote a patch that lets me set the IP/port for JSON-RPC in bitcoin.conf, I’ll send them 200 BTC. 😁
Related entries (1)
Related entries
Thank you jgarzik. The patch is working great, and I’ve sent the 200 BTC to the address in your signature.
Related entries (1)
Related entries
This doesn’t seem to be compatible with Slight change so that JSON-RPC binds to all/any IPs instead of just the loopback. (
http://bitcointalk.org/index.php?topic=611.msg11859#msg11859). Can these patches be combined or is one better than the other?Those two patches attempt similar things, and so should be considered mutually incompatible.
Yup, I’ve removed my patch, as jgarzik’s is better (mine was just a simple hack).
I’ve now removed jgarzik’s patch from my client in favor of using Satoshi’s -rpcallowip setting (since it’s in the vanilla svn).
Related entries (1)
Related entries
I’ve now removed jgarzik’s patch from my client in favor of using Satoshi’s -rpcallowip setting (since it’s in the vanilla svn).
But that doesn’t allow separate ports to run multiple clients on the same machine, does it?
That is correct, but my main concern was being able to connect to the JSON-RPC interface from somewhere other than localhost. Specifically so that I could manage my nodes with phpMyBitcoin.
Patch updated for latest SVN. Given recent upstream changes to support binding to any address (0.0.0.0 or ’*’), this patch is reduced to adding an option to bind or connect to a non-standard, not 8332 port:
URL:
http://yyz.us/bitcoin/patch.bitcoin-bindaddr
I’ve added the new bindaddr patch to my client.
