Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

Failure with IPv6 #740

Closed
daurnimator opened this issue Aug 30, 2021 · 1 comment
Closed

Failure with IPv6 #740

daurnimator opened this issue Aug 30, 2021 · 1 comment
Labels
kind/bug Something isn't working

Comments

@daurnimator
Copy link

daurnimator commented Aug 30, 2021

Version (k3OS / kernel)

k3os version v0.20.7-k3s1r0

5.4.0-73-generic #82 SMP Thu Jun 3 02:29:43 UTC 2021

Architecture

x86_64

Describe the bug

My network has both ipv4 and ipv6 connectivity; however k3os seems to pick up ipv6 first, and ignores ipv4:

I0830 17:33:25.632389    3857 node.go:172] Successfully retrieved node IP: 1234::1234
I0830 17:33:25.632482    3857 server_others.go:140] kube-proxy node IP is an IPv6 address (1234::1234), assume IPv6 operation
I0830 17:33:25.643111    3857 server_others.go:186] Using iptables Proxier.
F0830 17:33:25.643200    3857 server.go:495] unable to create proxier: CIDR 10.42.0.0/16 has incorrect IP version: expect isIPv6=true

To Reproduce

Expected behavior

Actual behavior

Additional context

Turning off ipv6 (sudo connman config myethernetdevice ipv6 off) allows k3s to boot.

@daurnimator daurnimator added the kind/bug Something isn't working label Aug 30, 2021
@dweomer
Copy link
Contributor

dweomer commented Oct 22, 2021

this should be a decent workaround in your system config:

boot_cmd:
- connman config myethernetdevice ipv6 off

@dweomer dweomer closed this as completed Oct 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants