Skip to content

Handle the addition or suppression of network interfaces/addresses #1823

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

Open
Hugal31 opened this issue Mar 12, 2025 · 0 comments
Open

Handle the addition or suppression of network interfaces/addresses #1823

Hugal31 opened this issue Mar 12, 2025 · 0 comments
Labels
new feature Something new is needed

Comments

@Hugal31
Copy link
Contributor

Hugal31 commented Mar 12, 2025

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 becomes tcp/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.

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

No branches or pull requests

1 participant