-
Notifications
You must be signed in to change notification settings - Fork 176
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
Zenoh should only consider UP and RUNNING network interfaces #573
Labels
enhancement
Existing things could work better
Comments
OlivierHecart
changed the title
Zenoh should only consider UP and RUNNING network interfaces
Zenoh should only consider Oct 26, 2023
UP
and RUNNING
network interfaces
OlivierHecart
changed the title
Zenoh should only consider
Zenoh should only consider UP and RUNNING network interfaces
Oct 26, 2023
UP
and RUNNING
network interfaces
OlivierHecart
added a commit
that referenced
this issue
Oct 26, 2023
Mallets
pushed a commit
that referenced
this issue
Oct 26, 2023
OlivierHecart
added a commit
that referenced
this issue
Jan 3, 2024
OlivierHecart
added a commit
that referenced
this issue
Jan 3, 2024
OlivierHecart
added a commit
that referenced
this issue
Jan 3, 2024
jerry73204
pushed a commit
to NEWSLabNTU/zenoh
that referenced
this issue
Jan 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
Zenoh by default binds listeners on
[::]
and advertises all ip addresses of allUP
interfaces to remote peers through scouting. This leads Zenoh to advertise addresses ofUP
but NOTRUNNING
network interfaces.Zenoh should only consider and advertise ip addresses of
UP
ANDRUNNING
network interfaces.The text was updated successfully, but these errors were encountered: