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.

Sign up for GitHub

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

Jump to bottom

Use default ULA prefix if fixed-cidr-v6 is not specified #47990

Open
robmry opened this issue Jun 14, 2024 · 0 comments
Open

Use default ULA prefix if fixed-cidr-v6 is not specified #47990

robmry opened this issue Jun 14, 2024 · 0 comments
Labels
area/networking/d/bridge area/networking/ipv6 Issues related to ipv6 area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Milestone
28.0.0

Comments

@robmry
Copy link
Contributor

robmry commented Jun 14, 2024 •
edited
Loading

Description

Custom bridge networks no longer need an IPv6 --subnet or entry in default-address-pools, if neither are specified the daemon will use a ULA prefix - #47853.

But, the default bridge still requires fixed-cidr-v6.

To make the default bridge less unusual - when ipv6 is set and fixed-cidr-v6 isn't, the default bridge should follow the same rules as a custom bridge.
@robmry robmry added kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny area/networking area/networking/ipv6 Issues related to ipv6 area/networking/d/bridge labels Jun 14, 2024
@robmry robmry added this to the 28.0.0 milestone Jun 14, 2024
@Zoey2936 Zoey2936 mentioned this issue Jun 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/networking/d/bridge area/networking/ipv6 Issues related to ipv6 area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Milestone
28.0.0
Development

No branches or pull requests
1 participant
@robmry