Skip to content
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

Issue #1701: Use a fallback to get interface state using the 'carrier' status #1719

Merged
merged 1 commit into from Feb 8, 2018

Conversation

rmetrich
Copy link
Contributor

Since some network drivers do not set the operstate value to down or up, we can fallback to using the carrier value:

  • failing to read the value means interface is administratively down
  • reading 0 means down
  • reading 1 means up

Copy link
Member

@jsmeix jsmeix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From plain looking at the code
it looks o.k. to me.

@jsmeix jsmeix requested a review from gdha February 7, 2018 12:43
@jsmeix jsmeix self-assigned this Feb 7, 2018
@jsmeix jsmeix added the enhancement Adaptions and new features label Feb 7, 2018
@jsmeix jsmeix added this to the ReaR v2.4 milestone Feb 7, 2018
@jsmeix
Copy link
Member

jsmeix commented Feb 7, 2018

@gdha
if you do not object, I would like to merge it tomorrorw.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features fixed / solved / done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants