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

Default network choice ... wonky? #81

Open
dwt opened this issue Mar 11, 2022 · 3 comments
Open

Default network choice ... wonky? #81

dwt opened this issue Mar 11, 2022 · 3 comments

Comments

@dwt
Copy link

dwt commented Mar 11, 2022

The default network choice to display seems wonky for me, my main interface (wlan) is en0 (Mac user here), but instead en5 is chosen for display, which has no ipv4 and only a very small part of the traffic going through it.

Not quite sure why that is and what the best way to choose a default interface with psutil would be, but right now this is a bit strange.

Also good enough as a workaround would be the ability to change the network interface from inside the app without having to restart it (and loose history that way).

@nschloe
Copy link
Owner

nschloe commented Mar 11, 2022

Yeah, tiptop isn't really made for dynamically choosing a network interface yet. I improved autoselection a bit (#83) so you get en0 by default. If that doesn't work, you can always use the --net argument on the command line.

@dwt
Copy link
Author

dwt commented Mar 15, 2022

Well, this sorta works. I now get the widget awdl0 chosen by default. I still think the real fix would be to choose the interface with most traffic as default. I guess that is something to look into how btop and others do this.

@nschloe
Copy link
Owner

nschloe commented Mar 15, 2022

Sure! Pull requests welcome.

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

2 participants