Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create dncore_network with private IP range (Installer) #547

Open
pablomendezroyo opened this issue Mar 10, 2023 · 3 comments
Open

Create dncore_network with private IP range (Installer) #547

pablomendezroyo opened this issue Mar 10, 2023 · 3 comments
Assignees
Labels
P1 Has to be done but not urgent security Related to security improvement

Comments

@pablomendezroyo
Copy link
Contributor

Create the docker dncore_network with a private IP range.

See

docker network create --driver bridge --subnet 172.33.0.0/16 dncore_network 2>&1 | tee -a $LOGFILE

@dsimog01 dsimog01 added P1 Has to be done but not urgent security Related to security improvement labels May 11, 2023
@pablomendezroyo
Copy link
Contributor Author

Should be done the last

@javyer
Copy link

javyer commented Sep 15, 2023

172.33.0.0/16 is not a local private network... Is there any reason why 172.33 was used ?
Private ranges is only : 172.16.0.0 to 172.31.255.255

@pablomendezroyo
Copy link
Contributor Author

@javyer Yes we know, that's why we are planning to migrate the IP range. It has been done like this since the beginning and now it would be harder to migrate. But we will!

@pablomendezroyo pablomendezroyo changed the title Create dncore_network with private IP range Create dncore_network with private IP range (Installer) Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Has to be done but not urgent security Related to security improvement
Projects
None yet
Development

No branches or pull requests

4 participants