You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: