slackhq/nebula

๐Ÿ› BUG: "Listener is IPv4, but writing to IPv6 remote" error is usually unhelpful

Opened this issue ยท 0 comments

What version of nebula are you using? (nebula -version)

1.9.4

What operating system are you using?

Linux

Describe the Bug

When the Lighthouse tells a host about an IPv6 address and it attempts to handshake, this error occurs if the host has IPv4 disabled or listen.host set to 0.0.0.0. This confuses a lot of users into thinking it's the cause of (whatever issues they happen to be having.)

Maybe we can make this message warning-level, debug-level, less frequent, more informative, or occur in fewer configurations?

Logs from affected hosts

n/a

Config files from affected hosts

n/a