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

Speaker crashloops on machine with IPv6 disabled #180

Closed
danderson opened this Issue Mar 4, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@danderson
Copy link
Member

danderson commented Mar 4, 2018

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

Make NDP announcer construction failure non-fatal. #180
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

Make NDP announcer construction failure non-fatal. #180
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

Correct the description of #180 in the release notes.
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

Correct the description of #180 in the release notes.
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

This comment has been minimized.

Copy link

jpiper commented Mar 4, 2018

Works for me!

@danderson danderson added this to the v0.5.0 milestone Mar 4, 2018

@danderson

This comment has been minimized.

Copy link
Member

danderson commented Mar 18, 2018

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.

danderson added a commit to danderson/metallb that referenced this issue Mar 18, 2018

Allow one of the layer2 protocol announcers to fail construction.
This makes the speaker work on v4-only or v6-only machines. It's a somewhat
unusual configuration that hard-disables IPv6 even in the kernel (which is
all we care about here), but it happens.

Fixes google#180

@danderson danderson closed this in 9c18e39 Mar 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment