[Network range migration] Connect all DAppNode packages to the two docker networks

[3alpha]

Intro

Currently, DAppNode internally uses 172.33.0.0/16 network range which is designated as public. It would be good to move away from that range so that any issues arising from that are avoided.

• private network name: dnprivate_network
• private network range: 10.20.0.0/24

Since DAppNode is highly modular system, migration will have to be done in multiple steps:

• Connect all DAppNode packages to the two docker networks
  • docker connect immediately on start + update the compose of the two issue
• Upgrade DNS resolver to use new network range
• Upgrade all packages that serve as access methods to the new range
• Test
• Test
• Remove old network

This issue concerns step one which will be starting point for all others steps.

Features expected

DAppManager connects itself and all other packages to the new docker network in the same manner it connects it self to the existing dncore_network.

[alexpeterson91]

10.20.0.0/24 will be the new range correct? the one already baked into wireguard?

[3alpha]

That is the plan, yes. Maybe we could've chosen block wiser both in terms of size and location.

[MysticRyuujin]

Why not either a) drop down to 172.32.0.0/16 or b) use a /16 off the 10.20.0.0?

Heck even better, make it configurable on initial setup for those of us with real networks where we might already use these ranges?

[alexpeterson91]

Making it configurable would involve a lot of work as it’s all hardcoded as is. It’s gonna be a few months just to change it to a new range. Making it user configurable would require a lot more work and make troubleshooting far more difficult. But we can explore that route i suppose. EDIT: Also the reason for 10.20.0.0/24 is just that its already been fully configured into the wireguard VPN package so the work is already done for that and it's an acceptable range, but we can put it to the devs and builders to vote on a block and size but that could just drive other issues with competing interests unrelated to dappnode.

[pablomendezroyo]

Another thing very important to take into account is that when moving to the new docker network dnprivate_network, the BIND container will have a different container IP than the current one 172.33.1.2. This IP is used in all the packages docker-compose files at the compose key dns

[pablomendezroyo]

IP range migration already implemented! needs to be published