osquery / osquery/osquery

macOS: `interface_details` table showing `0` in `link_speed`

Open
#6,595 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug macOS triage virtual tables
Dominant language
C++
Stars
23.6k
Forks
2.6k
Avg merge
6d 7h
Merged PRs (30d)
14

Description

Someone on slack commented that interface_details wasn't returning link_speed. A quick test on my mac confirms that behavior.

I haven't much dug into it, though I notice that it's all wrapped in a context.isColumnUsed("link_speed") and I wonder
what causes that to be true.

https://github.com/osquery/osquery/blob/29f4694df214bc3bd4e7210873e05bb19374888b/osquery/tables/networking/posix/interfaces.cpp#L189-L202

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in osquery/tables/networking/posix/interfaces.cpp around lines 189-202, where the issue observes the macOS link_speed behavior and context.isColumnUsed("link_speed") condition. Trace why link_speed is reported as 0 on macOS, then verify the interface_details output on macOS after the behavior is corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
networking, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.