-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
net: add Sys field to Interface for retrieving platform-specific information #17445
Comments
Can you please create a reproducing case for this that does not involve an external repository? |
@robpike updated to invoke |
Any good use case of IFLA_IFALIAS doesn't come to my mind.
Besides current API doesn't expose such platform-specific information for consistency across platforms; for example, it never displays information related to route-labels, similar to IFLA_IFALIAS of Linux, on OpenBSD. I'm fine to have x/net/netlink package for some Linux-specific use case as we have x/net/route for BSD variants, but I'm not keen to add support for IFLA_IFALIAS into net package. |
@mikioh I'll admit the internet's not been much help in explaining an intended use of
That the |
For pure management plane or hybrid control/management plane stuff, how about this?
|
@mikioh, and I assume the |
Are interface aliases in the same namespace as interface names? Can I add the alias |
On Linux IFLA_IFALIAS is an attribute that represents an opaque string member in netdevice structure. It doesn't collaborate with any control plane process.
Yes. |
I'd like to see |
@mikioh If alias aren't used as a direct alias for interface names in InterfaceByName then I'd be fine with any implementation that allows me to associate an application role with an interface. Aliases seemed a neat way of doing so. Bit of background - I'm associating various aspects of the system with application level roles so that one program can set those up, and others can use a known name at build time to acquire the XXX that they need. |
Do you want to see this Sys feature in Go 1.8? Or not so rush? |
Perhaps, you can share your pain with people who are working on NETCONF+NETMOD, ASN.1+MIB+SNMP, Telcordia or 3GPP OSS/BSS stuff. ;) |
31st October is the cut-off day for Go 1.8, so this doesn't happen in Go 1.8. |
@mikioh Apologies for the silence - we've had to take an alternate path already so no rush. |
Change https://golang.org/cl/162037 mentions this issue: |
What version of Go are you using (
go version
)?go version go1.7 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
What did you see instead?
If
InterfaceByName
doens't check aliases on systems that support them then interface aliases become problematic. If you have to know that the name is an aliases it defeats the point.The text was updated successfully, but these errors were encountered: