|
Title: Docker's bridge network bitcoind's banned Post by: adys11 on December 30, 2017, 07:11:06 PM Hi,
I am running bitcoind on docker (windows 10). RPC is working good. I am getting a lot of banning messages for docker bridge address, on all ports. 2017-12-30 19:07:50 connection from 172.17.0.1:51902 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51904 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51906 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51908 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51910 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51912 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51914 dropped (banned) 2017-12-30 19:07:50 connection from 172.17.0.1:51916 dropped (banned) And so on for all the ports. I am not the first to encounter this. https://github.com/amacneil/docker-bitcoin/issues/32 (https://github.com/amacneil/docker-bitcoin/issues/32) Any idea how to solve it? Thanks, Ady. Title: Re: Docker's bridge network bitcoind's banned Post by: Anti-Cen on December 31, 2017, 08:55:25 PM Firewall maybe
I take it your running a full node and are using RPC to talk to the client here ? Title: Re: Docker's bridge network bitcoind's banned Post by: Foxpup on January 01, 2018, 01:33:09 AM It should probably be considered a bug that Bitcoin Core can ban non-routable addresses. As a workaround, putting "whitelist=172.16.0.0/12" in bitcoin.conf should work (after restarting bitcoind and clearing the existing bans).
|