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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: