-
Notifications
You must be signed in to change notification settings - Fork 497
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
(FACT-1592) A key/value pair for Interface Speed/Duplex #2480
Conversation
Can one of the admins verify this patch? |
For the record, I'd like to see this functionality. It looks useful for day-to-day work. |
f58b1ef
to
199809c
Compare
199809c
to
86622c0
Compare
86622c0
to
533ff31
Compare
533ff31
to
4b0aa25
Compare
4b0aa25
to
d35a77e
Compare
629e071
to
66ef22a
Compare
66ef22a
to
b86e723
Compare
Updated |
I disabled the |
b86e723
to
9a4557b
Compare
rebased |
1115a9c
to
55adeca
Compare
2b4350e
to
7df3bf0
Compare
4c6ec37
to
01f02e3
Compare
01f02e3
to
372aa59
Compare
Signed-off-by: Pat Riehecky <[email protected]>
372aa59
to
a5267b3
Compare
I made a slight modification to a5267b3, added a refactor commit and opened a new PR to supersede this one. Thank you for your contribution (and patience!) |
I'll confess, I'll need help with the tests....
This partially resolves the issue for Linux systems.
Facter will have a
speed
fact equal to the link speed determined by the kernel for each supported interface.Facter will have a
duplex
fact equal to the duplex determined by the kernel for each supported interface.For wired networks this should report the speed/duplex even if the interface is not assigned an address.