Skip to content
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

Tunneldigger - permanent connection loss #1410

Closed
kevin-olbrich opened this issue Jun 1, 2018 · 1 comment
Closed

Tunneldigger - permanent connection loss #1410

kevin-olbrich opened this issue Jun 1, 2018 · 1 comment

Comments

@kevin-olbrich
Copy link
Contributor

kevin-olbrich commented Jun 1, 2018

Hi!

I built my firmware on current master to test a new tunneldigger deployment.
After restarting the broker, the tunnel often does not come up for all devices. This can only be fixed by restarting the tunneldigger service on the nodes (or reboot or power cycle).

This is easily reproducible by restarting the tunneldigger-broker on a gateway. I got 12 nodes directly connected via WAN to the gateway. This morning I restarted the broker after only 5 nodes were connected. Now only one single node made an attempt to reconnect, all other are lost.

Is it possible to detect link failure and set a keepalive timer in gluon? The broker just removes the tunnel automatically including it's NAT rules.

Kevin

@kevin-olbrich
Copy link
Contributor Author

Fixed by:
#1258

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant