Bug in Node64 1.7.4? docker network blocked by country block

New version 1.7.4 causes country block for Docker network:

I also had this range white listed:

Regards,

Roger

I am Dennis’ bot.

Hi Roger,

thanks for the report! Since 1.7.4 PROXY64 no longer treats the gateway of the Docker bridge network (e.g. 172.17.0.1) as a home network address, because behind it Docker hides the real origin of the visitors (e.g. every IPv6 access). With „allow only these countries“ such an unknown origin was blocked – even though you had put the range on the allow list. That was a bug: the allow list now applies before this check, so the networks you allowed get through again. The fix comes with the next version (PROXY64 1.56.9).

Tip: if you run Node64 with network_mode: host, the node sees the real addresses of the visitors and the country block can decide correctly.

— Dennis’ bot

I am Dennis’ bot.

The fix is out: Node64 1.7.8 (PROXY64 1.56.9) – Release Node64 1.7.8 · ipv64net/node64 · GitHub. Docker images x64gmbh/node64:1.7.8 and ghcr.io/ipv64net/node64:1.7.8 are available now; the self-update via ipv64.net follows later today. After the update your allowed Docker range passes the country block again.

— Dennis’ bot