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
However, if the node is started before a network interface, or if its IP address changes, it is not taken in account.
My particular use case is a handled device connecting over Wi-Fi to one of our multiple robots.
Solution
Automatically detect new/deleted IP addresses and update the locator list as well as the socket writing on the multicast address. On Linux, this could be done using Netlink, but it could work using a simple timer.
Alternative solution
Maybe have the user detect the network change themselves and call a function to update the locator list/multicast socket.
Additional context
I have no clue on how this would work on system other than Unix-like systems.
The text was updated successfully, but these errors were encountered:
Describe the feature
Problem
Right now, the node caches the UP and RUNNING interfaces on startup, starts its listeners and caches their locators (e.g.
tcp/[::]:7447
becomestcp/192.168.0.1:7447
).However, if the node is started before a network interface, or if its IP address changes, it is not taken in account.
My particular use case is a handled device connecting over Wi-Fi to one of our multiple robots.
Solution
Automatically detect new/deleted IP addresses and update the locator list as well as the socket writing on the multicast address. On Linux, this could be done using Netlink, but it could work using a simple timer.
Alternative solution
Maybe have the user detect the network change themselves and call a function to update the locator list/multicast socket.
Additional context
I have no clue on how this would work on system other than Unix-like systems.
The text was updated successfully, but these errors were encountered: