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
{{ message }}
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.
After moving a helium router (console) to a different server with a different IP address, the hotspot fleet still use the previous IP address even 24h later. this prevent the LoRaWan traffic to be routed. Devices lost communications.
When a hotspot is rebooted it immediately take the new router/console address and the communication is restored... but we can't reboot all the hostpots to get the tables updated.
The text was updated successfully, but these errors were encountered:
disk91
changed the title
Router IP does not update until miner reboot (or is too long for updating)
Helium Router IP does not update until miner reboot (or is too long for updating)
Oct 18, 2022
Apparently some miners have been updated with the new IP about 30h after the change. I now see two miners getting the messages. The problem is now the refresh time.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After moving a helium router (console) to a different server with a different IP address, the hotspot fleet still use the previous IP address even 24h later. this prevent the LoRaWan traffic to be routed. Devices lost communications.
When a hotspot is rebooted it immediately take the new router/console address and the communication is restored... but we can't reboot all the hostpots to get the tables updated.
The text was updated successfully, but these errors were encountered: