Bug 512848 - Not all IPv6 addresses are visible
Summary: Not all IPv6 addresses are visible
Status: RESOLVED DUPLICATE of bug 509743
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.5.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-01 21:17 UTC by Szymon Łągiewka
Modified: 2025-12-02 10:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
widget without GUA shown (115.20 KB, image/png)
2025-12-01 21:17 UTC, Szymon Łągiewka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Łągiewka 2025-12-01 21:17:53 UTC
Created attachment 187295 [details]
widget without GUA shown

SUMMARY
Depending on (likely some random) circumstances, the network widget shows my public IPv6 address (GUA) or IPv6 ULA address, but never both.

My host has 2 GUAs, 2 ULAs from my internal prefix and 1 ULA from Tailscale. 

STEPS TO REPRODUCE
1. Have an IPv6 host with both GUA and ULA IPv6 addresses.
2. Open the network widget 
3. Choose your connection
4. Open the Details tab

OBSERVED RESULT
Either GUA or ULA is shown

EXPECTED RESULT
Ideally, all addresses are shown

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.9

ADDITIONAL INFORMATION
nmcli output
```
❯ nmcli device show enp1s0
GENERAL.DEVICE:                         enp1s0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Wired connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/2
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         172.16.127.133/16
IP4.GATEWAY:                            172.16.0.1
IP4.ROUTE[1]:                           dst = 172.16.0.0/16, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 172.16.0.1, mt = 100
IP4.DNS[1]:                             172.16.0.1
IP4.DOMAIN[1]:                          localdomain
IP6.ADDRESS[1]:                         fd69:dead:beef:snipped/64
IP6.ADDRESS[2]:                         2a01:114f:snipped/64
IP6.ADDRESS[3]:                         2a01:114f:snipped/64
IP6.ADDRESS[4]:                         fd69:dead:beef:snipped/64
IP6.ADDRESS[5]:                         fe80::snipped/64
IP6.GATEWAY:                            fe80::snipped
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 1024
IP6.ROUTE[2]:                           dst = fd69:dead:beef::/64, nh = ::, mt = 100
IP6.ROUTE[3]:                           dst = 2a01:114f:snipped::/64, nh = ::, mt = 100
IP6.ROUTE[4]:                           dst = ::/0, nh = fe80::snipped, mt = 100
IP6.DNS[1]:                             2a01:114f:snipped::1
```
Comment 1 David Redondo 2025-12-02 10:38:04 UTC

*** This bug has been marked as a duplicate of bug 509743 ***