On 2023-02-17 02:06, Stakanov wrote:
In data venerdì 17 febbraio 2023 00:13:01 CET, kschneider bout-tyme. net ha scritto:
lo == loopback interface.
...
Anybody knows what is the use of "lo" and what is going on?
well, I am still troubled, because I simply do not understand why the lo was not present before and now it appeared. I am also having problems with my network setup. The usecase of lo in my PC is not something I would expect to request the presence of an lo. But since another instance I have of TW also shows now a lo interface, I think this was an update that made it appear. I am just not understanding to what purpose.
I see "lo" since ever. Decades ago. cer@Telcontar:~> ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.14 netmask 255.255.0.0 broadcast 192.168.255.255 inet6 fe80::2d8:... prefixlen 64 scopeid 0x20<link> ether 00:d8:61:a1:5a:bd txqueuelen 1000 (Ethernet) RX packets 1918666 bytes 1387107591 (1.2 GiB) RX errors 0 dropped 3470 overruns 0 frame 0 TX packets 1469968 bytes 250810218 (239.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1071607 bytes 177021090 (168.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1071607 bytes 177021090 (168.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)