[Bug]:Insight –> NoName does not identify applications sharing an IP/FQDN
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- swift
- Domain
- desktop, networking
Research direction
Start in the Insight → NoName view and trace how its IP/FQDN entries are built and presented; the issue does not name source files or tests. Find where the entry’s associated applications and connection counts are available, then check how other Insight entries support selection or drill-down. Done means selecting an IP/FQDN reveals the associated application names and paths, with connection counts when available.
Written by the indexing model from the issue text.
Description
Area
rules
macOS version
macOS 15.8.3
FreeSnitch version/build
1.1.0 (34)
Current mode
Alert
Expected behavior
Users should be able to click an IP/FQDN entry and see the applications associated with it.
Ideally, the interface should display:
- Application name.
- Application executable/path.
- Associated IP address or FQDN.
- Number of connections, if available.
Actual behavior
In Insight → NoName, FreeSnitch indicates that an IP address or FQDN is being used by two or more applications.
However, the interface does not provide any information about which applications are actually using that IP address or FQDN.
The entry is also not clickable, so there is no way to drill down and retrieve additional information.
Steps to reproduce
see Insight -> NoName
Logs
- Dominant language
- Swift
- Stars
- 49
- Forks
- 5
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 82
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from isaaclins/freesnitch
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
isaaclins/freesnitch#428 ·
Maintainers usually reply within 1 day
-
area:shared bug priority:high status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
isaaclins/freesnitch#284 ·
Maintainers usually reply within 1 day
-
area:helper bug priority:medium status:queued type:diagnostics
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
isaaclins/freesnitch#282 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
isaaclins/freesnitch#281 ·
Maintainers usually reply within 1 day
All issues in isaaclins/freesnitch
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day