Skip to content
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

Interface picking logic is fuzzy with VPNs #2090

Open
msanft opened this issue Oct 7, 2024 · 0 comments
Open

Interface picking logic is fuzzy with VPNs #2090

msanft opened this issue Oct 7, 2024 · 0 comments

Comments

@msanft
Copy link

msanft commented Oct 7, 2024

In the netlink implementation, only the default interface is considered for display in the status bar.

In some cases, I believe this to be sub-optimal. Consider a case where someone uses a non-permanent (e.g. company) VPN together with a normal network connection. The wired / wifi connection will be the default interface, as it's the permanent connection everything except the VPN traffic gets routed through, so this will also be the interface used in the status bar. However, users would be more likely to be interested in the VPN being (in)active in that case. I can rarely imagine a case where a VPN would be the default interface.

I suggest to instead consider all connected interfaces (except for the loopback, probably), and see if a "special" interface (i.e. tuntap / wg / ppp) is being used, displaying that with precedence over the default interface, or just adding a separate information source on whether a VPN interface is active so that it can be used in the bar.

What do you think about this? If my proposal sounds fine to you, I'd volunteer to implement it.

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

No branches or pull requests

1 participant