Skip to content

feat: add rfkill network setting #4260

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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

notpeelz
Copy link
Contributor

@notpeelz notpeelz commented Jul 2, 2025

This setting makes it possible to have a configuration with two network modules where one of them displays the ethernet state (disconnected, linked, ethernet), and the other, the wifi state (disabled, disconnected, linked, wifi).
Otherwise the ethernet state would show up as "disabled" (instead of "disconnected") when rfkill is active.

@notpeelz notpeelz force-pushed the feat-display-rfkill-setting branch from d69b3a4 to 8473e94 Compare July 2, 2025 04:08
@notpeelz notpeelz changed the title feat: add display-rfkill network setting feat: add rfkill network setting Jul 2, 2025
@notpeelz notpeelz force-pushed the feat-display-rfkill-setting branch 2 times, most recently from 68bd3e4 to 24d9ca5 Compare July 3, 2025 20:52
notpeelz added 7 commits July 10, 2025 08:01
We want the "disabled" state even when an interface is selected
explicitly.
This setting makes it possible to have a configuration with two
network modules where one of them displays the ethernet state
(disconnected, linked, ethernet), and the other, the wifi state
(disabled, disconnected, linked, wifi).

Otherwise the ethernet state would show up as "disabled" (instead of
"disconnected") when rfkill is active.
Some fields were previously uninitialized (e.g. carrier), which
could lead to UB.
I'm not sure why, but my network card (mt7921e) sometimes will report
having a carrier when the interface is down. This usually happens
when rfkill was active before rebooting.
@notpeelz notpeelz force-pushed the feat-display-rfkill-setting branch from 24d9ca5 to 73d9c5f Compare July 10, 2025 12:01
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.

1 participant