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.4
What operating system are you using?
Mac
Describe the Bug
Nebula connects and works fine on Mac. I am running from within a Docker container, using bridge networking. After I close my laptop, go away, and come back it occasionally fails to reconnect (after the Mac sleeps/hibernates/whatever Mac does), showing Handshake timed out. From inside the container, I can reach all the UDP sockets of the lighthouse, if I run the same container again with the same config it starts and connects fine, but for some reason the original container that was left running is unable to connect.
It seems calling a config reload fixes the issue without restarting the container, although as it’s a hard issue to replicate I have only been able to confirm that once:
func (c *C) ReloadConfig() {
Is there something that the ReloadConfig() is doing that isn't done during a timeout? Perhaps NAT tables shift in Docker when it wakes back up and the UDP connection needs re-establishing? Any thoughts to help debug this one appreciated.
What version of
nebula
are you using? (nebula -version
)1.9.4
What operating system are you using?
Mac
Describe the Bug
Nebula connects and works fine on Mac. I am running from within a Docker container, using bridge networking. After I close my laptop, go away, and come back it occasionally fails to reconnect (after the Mac sleeps/hibernates/whatever Mac does), showing
Handshake timed out
. From inside the container, I can reach all the UDP sockets of the lighthouse, if I run the same container again with the same config it starts and connects fine, but for some reason the original container that was left running is unable to connect.It seems calling a config reload fixes the issue without restarting the container, although as it’s a hard issue to replicate I have only been able to confirm that once:
Is there something that the
ReloadConfig()
is doing that isn't done during a timeout? Perhaps NAT tables shift in Docker when it wakes back up and the UDP connection needs re-establishing? Any thoughts to help debug this one appreciated.Logs from affected hosts
Config files from affected hosts
Potentially related to rebinding that I think only ever landed for ios? #394
The text was updated successfully, but these errors were encountered: