On 18.02.2023 18:41, Stakanov wrote: ...
And to make it more curious when I hover over the symbol of the Network manager in the tray, I DO(!) see three cabled ethernet lo, cabled ethernet enp7s0 and br0 interfaces. But not in the list of interfaces when I open it, there just lo and br0
Is this intentional? (If you happen to know of course).
No idea. You do not even tell what desktop environment you are using or what program is behind "symbol of the Network manager".
Show output of
LANGUAGE=C PAGER= nmcli device LANGUAGE=C PAGER= nmcli connection
entropy@localhost:~> LANGUAGE=C PAGER= nmcli device DEVICE TYPE STATE CONNECTION br1 bridge connected br1 lo loopback connected (externally) lo enp7s0 ethernet connected enp7s0
br1 061ef80f-f74b-3e4c-bd33-b4af9a4ab0ca bridge br1 lo ad2a8122-d824-4459-8b33-927bff6595da loopback lo enp7s0 8ed855e5-8e0a-3c75-ba6c-c2bca7c86f32 ethernet enp7s0 br0 dd45b56c-398d-4539-8369-aa6199c0df7f bridge -- enp8s0 c9325210-a630-39f4-a1d8-2ea015bf274a ethernet --
Operating System: openSUSE Tumbleweed 20230217 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD FX(tm)-4300 Quad-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon Pro W5500 Manufacturer: Gigabyte Technology Co., Ltd.
The symbol in the tray is the "nmapplet" showing in Plasma as "networkmanagerapplet" in the tray. enp7s0 ethernet connected enp7s0
As far as I can tell, tool tip shows active connection profiles and when you open applet it shows "filtered" connection profiles - you are not supposed to manage bridge slave directly (from the Plasma applet developers PoV) so applet hides it. When connection profiles are named like interfaces it becomes rather confusing. Of course showing "Wired Ethernet: connected to lo" is wrong - "lo" has type "loopback", not "Ethernet". But Plasma applet is not part of NetworkManager; it is completely separate project. So no wonder it lags behind NetworkManager changes. You may consider opening bug report on KDE bugtracker. Also strictly speaking "connected to bridge" is inaccurate as well - for virtual interfaces they are created as part of profile activation, there is nothing to "connect to" before profile is active. It were also more useful to show actual interface names ... and so on, there is certainlyroom for improvement.
did show in the connection window of the applet before, but since the upgrade it does not.
What means "externally connected" in relation with lo?
It means that NetworkManager adopted interface configuration that existed when NetworkManager was started; it was not actively configured by NetworkManager itself.
I thought this is just locally connected?