-
-
Notifications
You must be signed in to change notification settings - Fork 765
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
network module only shown ipv6 address #3956
Comments
I can reproduce the issue |
Same for me. I think this happened after updating $ uname -a
Linux sebastian-t480s 6.12.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.12-1 (2025-02-02) x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/" |
It seems that this commit has removed support for the Why?! |
@gustafullberg maybe? |
Reproducible with waybar 0.12.0 on Tumbleweed |
same for me on debian and waybar 0.12.0 |
As it appears, your commit seems to be breaking support for ipv4 addresses in waybar @gustafullberg. Could you please undo it? Why did you remove support for ipv4 in the first place? |
Seems like there is an issue with interfaces having both ipv4 and ipv6 addresses. We should probably add the option config["family"] back to let people limit to only ipv4 or ipv6. |
I am also having this issue. |
Would also be nice to control which ipv6 address is displayed, although perhaps not trivial. It's currently showing a SLAAC address, but there's also a shorter dhcpv6 address that I would prefer to use instead. |
When will this be fixed? The family option is mentioned in documentation and its very confusing and misleading |
same issuue after rename net card interface |
could there also be an option do display both? To have ipv4 and ipv6 as separate variables? So you could configure a tooltip that shows you both addresses (when available)? |
#3809
Even after setting family to ipv4
The text was updated successfully, but these errors were encountered: