In data sabato 18 febbraio 2023 07:15:25 CET, Andrei Borzenkov ha scritto:
On 18.02.2023 03:05, Stakanov wrote:
In data venerdì 17 febbraio 2023 05:10:19 CET, Andrei Borzenkov ha scritto:
On 17.02.2023 01:55, Stakanov wrote:
what is the meaning of the "lo" interface that appeared on my networkmanager.
https://networkmanager.dev/blog/networkmanager-1-42/
And scroll to the Managing the loopback interface.
I also looked what is about wicked but for some reasons wicked seems gone?
Not really understanding, I did not see any update that required to uninstall wicked.
Anybody knows what is the use of "lo" and what is going on?
Thank you, and this was a supplemental interesting reading.
I have to admit that I struggle to see if it is a usecase for me or not.
With the loopback interface always guaranteed to exist in one instance, a connection on a loopback interface can be used to specify configuration that’s always supposed to be applied. This includes things like adding an extra IP address or perhaps a DNS server.
Humm, not that I am very good in networking but as far as I understand what is written the use of lo is a kind of constituting a "template"?
I find the new behavior a bit confusing. Before I had the ethernet cabled connection set up without IP to be used via the bridge (and that bridge would then serve and is necessary to me, as interface for my KVM virtual machines.
Now however I have the loopback interface that is always there and always connected....to 127.0.0.1 but...my cabled ethernet connection is not shown anymore in the list, only lo and br0. 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 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? I thought this is just locally connected?