Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upnet: add FlagRunning as network interface flag #29991
Comments
gopherbot
added this to the Proposal milestone
Jan 30, 2019
gopherbot
added
the
Proposal
label
Jan 30, 2019
This comment has been minimized.
This comment has been minimized.
CC @mikioh |
This comment has been minimized.
This comment has been minimized.
Looks like reporting just |
This comment has been minimized.
This comment has been minimized.
Reading through the code review and I couldn't find anything that speaks against supporting |
This comment has been minimized.
This comment has been minimized.
It seems like we should have the bit since it's part of the standard network API. Accepting. |
rsc
added
the
Proposal-Accepted
label
Feb 6, 2019
rsc
changed the title
proposal: net: add FlagRunning as network interface flag
net: add FlagRunning as network interface flag
Feb 6, 2019
rsc
modified the milestones:
Proposal,
Go1.13
Feb 6, 2019
ianlancetaylor
added
help wanted
NeedsFix
labels
Feb 6, 2019
This comment has been minimized.
This comment has been minimized.
The current set of net.Flags are chosen from the following criteria:
IIUC, IFF_RUNNING was introduced in BSD variants to represent some state of My recommendation as follows:
|
This comment has been minimized.
This comment has been minimized.
http://golang.org/cl/162037 is a counter proposal. |
brutella commentedJan 30, 2019
FlagUp
doesn't tell if for example an ethernet cable is physically attached to a network interface.According to the IFF_UP vs IFF_RUNNING answer, the flag
IFF_RUNNING
actually does that.(I did not verify this.)
I propose to add
net.FlagRunning
to know if a network interface is operational.