Skip to content

Speaker crashloops on machine with IPv6 disabled #180

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

Closed
danderson opened this issue Mar 4, 2018 · 3 comments
Closed

Speaker crashloops on machine with IPv6 disabled #180

danderson opened this issue Mar 4, 2018 · 3 comments
Assignees
Milestone

Comments

@danderson
Copy link
Contributor

The NDP announcer causes a hard failure if there is no link-local IPv6 address on the listening interface. This notably breaks RHEL7 and OEL7, because they're quite old and apparently have IPv6 hard-disabled in the kernel, so even link-local autoconfig doesn't happen.

@danderson danderson self-assigned this Mar 4, 2018
danderson added a commit that referenced this issue Mar 4, 2018
Some machines have zero IPv6 support, including link-local addresses.
We need to fail gracefully in that scenario.
danderson added a commit that referenced this issue Mar 4, 2018
Some machines have zero IPv6 support, including link-local addresses.
We need to fail gracefully in that scenario.

(cherry picked from commit 8f6bdae)
danderson added a commit that referenced this issue Mar 4, 2018
The issue is actually just systems with hard-disabled IPv6, but the
default RHEL (and therefore probably OEL) kernels *do* have IPv6
enabled.
danderson added a commit that referenced this issue Mar 4, 2018
The issue is actually just systems with hard-disabled IPv6, but the
default RHEL (and therefore probably OEL) kernels *do* have IPv6
enabled.

(cherry picked from commit 8d6db88)
@jpiper
Copy link

jpiper commented Mar 4, 2018

Works for me!

@danderson danderson added this to the v0.5.0 milestone Mar 4, 2018
@danderson
Copy link
Contributor Author

Yeah, discussion in slack concluded that this is specific to one environment, where network/sys ops completely disabled IPv6 for some reason.

I still want speaker to fail gracefully if one of the protocol families doesn't work.

@Russell-IO
Copy link

@danderson I think that I'm hitting this bug, out networking team disable IPv6 as Standard on all hosts, and it doesn't seem to advertise the root, if I enable IPv6, it works

karampok pushed a commit to karampok/metallb that referenced this issue Jun 20, 2024
ci: fix registry auth error and go version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants