You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of nebula are you using? (nebula -version)
1.9.2
What operating system are you using?
Linux
Describe the Bug
While debugging an issue on Nebula OSS I saw confusing behavior where a host reported "Handshake message sent" with a vpnIp field equal to its own IP address. This was followed by "Refusing to handshake with myself."
On Linux, when attempting to connect to your own IP address, it will typically send traffic over the loopback interface. Therefore it's unexpected that we would see Nebula try to handshake with its own IP address. It seems that this can occur when a host configures itself as a via for an unsafe_routes entry.
I think this is probably always a misconfiguration - maybe we should spit out an error if we detect the host's own IP address in a via at startup / reload time?
What version of
nebula
are you using? (nebula -version
)1.9.2
What operating system are you using?
Linux
Describe the Bug
While debugging an issue on Nebula OSS I saw confusing behavior where a host reported "Handshake message sent" with a
vpnIp
field equal to its own IP address. This was followed by "Refusing to handshake with myself."On Linux, when attempting to connect to your own IP address, it will typically send traffic over the loopback interface. Therefore it's unexpected that we would see Nebula try to handshake with its own IP address. It seems that this can occur when a host configures itself as a
via
for anunsafe_routes
entry.I think this is probably always a misconfiguration - maybe we should spit out an error if we detect the host's own IP address in a
via
at startup / reload time?Logs from affected hosts
Config files from affected hosts
n/a
The text was updated successfully, but these errors were encountered: