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

Decrease network size of Docker default bridge (#2135) #2246

Merged
merged 1 commit into from
Nov 25, 2022

Conversation

agners
Copy link
Member

@agners agners commented Nov 25, 2022

Instead of allocating 172.17.0.0/16 as the default network bridge use a much smaller range. This helps folks which have hosts in that network range.

Ideally, we should make the default as well as the hassio bridge configurable.

@agners agners added the os label Nov 25, 2022
@agners agners requested a review from pvizeli November 25, 2022 11:05
@agners agners changed the title Decrease network size of Docker default bridge Decrease network size of Docker default bridge (#2135) Nov 25, 2022
@agners
Copy link
Member Author

agners commented Nov 25, 2022

This relates to #2135.

@agners agners merged commit ce16ee5 into home-assistant:dev Nov 25, 2022
@agners agners added the REL-9 label Nov 29, 2022
@SolarstormTM
Copy link

SolarstormTM commented Dec 9, 2022

The class b private adresses can go from 172.16.0.0 - 172.31.255.255 maybe picking the a space like 172.25.0.0/16 would slim the chances of someone using that subnet.
It sure would help on my network 172.17.0.0/16

@agners
Copy link
Member Author

agners commented Dec 10, 2022

@SolarstormTM right good point, we use 172.30.32.0/23 for the hassio bridge network. So I'd suggest to use 172.30.232.1/23 then, so we use the same class B network.

@agners agners deleted the adjust-default-bridge-ip branch December 10, 2022 12:48
agners added a commit to agners/operating-system that referenced this pull request Dec 10, 2022
Use a subnet in the same class B network for the Docker default bridge
is using. This avoids conflicting with more than one class B network.
@agners
Copy link
Member Author

agners commented Dec 10, 2022

PR #2259

agners added a commit that referenced this pull request Dec 10, 2022
Use a subnet in the same class B network for the Docker default bridge
is using. This avoids conflicting with more than one class B network.
@dilorenzo1987
Copy link

It would be helpful to also mention the range change in the title because it broke by SSH Port Forwarding Addon :)

@ThomDietrich
Copy link

@dilorenzo1987 fixed via ThomDietrich/home-assistant-addons#11 Thanks @hnykda

agners added a commit that referenced this pull request Jan 24, 2023
Use a subnet in the same class B network for the Docker default bridge
is using. This avoids conflicting with more than one class B network.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants