Skip to content

fix: exclude dummy interfaces from system interfaces list and ensure …#244

Open
DanielLavrushin wants to merge 3 commits into
mainfrom
1-66-1-fixes
Open

fix: exclude dummy interfaces from system interfaces list and ensure …#244
DanielLavrushin wants to merge 3 commits into
mainfrom
1-66-1-fixes

Conversation

@DanielLavrushin
Copy link
Copy Markdown
Owner

…they are included in monitoring options

Copilot AI review requested due to automatic review settings June 7, 2026 21:15
@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Jun 7, 2026

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics -9 complexity

Metric Results
Complexity -9

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes interface discovery so Linux dummy* interfaces (e.g., dummy0) appear in Settings interface selectors (monitoring / NAT masquerade), instead of being filtered out.

Changes:

  • Stop excluding dummy* interfaces via the “virtual/internal” exclude-prefix list.
  • Treat dummy* as an allowed interface prefix even when it has no IP assigned (host mode), so it still shows up in selectors.
  • Document the fix in changelog.md as 1.66.1.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/http/handler/config.go Adjusts interface filtering rules to include dummy* interfaces in the returned interface list.
changelog.md Adds a 1.66.1 entry describing the dummy-interface list fix.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/http/handler/config.go Outdated
Copilot AI review requested due to automatic review settings June 7, 2026 23:13
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Comment thread changelog.md
- FIXED: **b4 would not start on some Asus Merlin routers** - on certain firmware (for example the MerlinWRT) b4 quit right after starting and showed a confusing message about a missing `xt_connbytes` feature, even though the router actually supported it. The real cause was b4 using a newer firewall command option that the router's built-in tool did not understand. b4 now adapts to the router's own tools automatically, so it starts normally with nothing extra to install.
- FIXED: **Telegram no longer disconnects with a "proxy is not configured correctly" message after sitting idle** - when a Telegram connection through b4 was left idle for a while, your network could quietly drop it in the background, and Telegram would show "The proxy you are using is not configured correctly and will be disabled" even though the proxy was working fine. b4 now keeps these connections alive on its own, so they stay open and reconnect cleanly instead of being dropped.
- FIXED: **Connections page showed nothing when the device clock was out of sync** - the time filter (30s / 1m / 5m / 15m) and the per-connection activity graph compared the live data against the browser's own clock, so a computer whose clock was off by even ~30 seconds could see an empty list and empty activity bars. Filtering and the activity graph now use the timestamps in the connection data itself, so they work regardless of the device clock or its timezone.
- FIXED: **b4 would not start on some Asus Merlin routers** - on certain firmware (for example the MerlinWRT) b4 quit right after starting and showed a confusing message about a missing `xt_connbytes` feature, even though the router actually supported it. The real cause was b4 using a newer firewall command option that the router's built-in tool did not understand. b4 now adapts to the router's own tools automatically, so it starts normally with nothing extra to install.- FIXED: **Connections page showed nothing when the device clock was out of sync** - the time filter (30s / 1m / 5m / 15m) and the per-connection activity graph compared the live data against the browser's own clock, so a computer whose clock was off by even ~30 seconds could see an empty list and empty activity bars. Filtering and the activity graph now use the timestamps in the connection data itself, so they work regardless of the device clock or its timezone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants