Skip to content
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.

Helium Router IP does not update until miner reboot (or is too long for updating) #1833

Open
disk91 opened this issue Oct 18, 2022 · 1 comment

Comments

@disk91
Copy link

disk91 commented Oct 18, 2022

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.

@disk91 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
@disk91
Copy link
Author

disk91 commented Oct 19, 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant