El 26/12/18 a las 1:07, Lisandro Damián Nicanor Pérez Meyer escribió: > Hi Santiago! > > El mar., 25 dic. 2018 19:57, Santiago José López Borrazás <sjlop...@gmx.es > <mailto:sjlop...@gmx.es>> escribió: > > El 25/12/18 a las 23:31, Lisandro Damián Nicanor Pérez Meyer escribió: > > > > I mean your internet loopback device. Please send the output of > > > > ip addr > > sjlopezb@local:~$ ip addr > > (...) > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP group default qlen 1000 > link/ether 00:1d:09:dd:a9:3e brd ff:ff:ff:ff:ff:ff > inet 192.168.1.45/24 <http://192.168.1.45/24> brd 192.168.1.255 > scope global eth0 > valid_lft forever preferred_lft forever > inet6 fe80::21d:9ff:fedd:a93e/64 scope link > valid_lft forever preferred_lft forever > sjlopezb@local:~$ > > It is not a problem of routes. It's not a network problem either, because > I'm using wicd. > > Network works perfect. > > > I'm not asking for eth0 but the loopback (lo) interface. KDE needs it up > and running to work. > > These days it's normal to have it in place, but it's safer to check :-)
In local I have no problem (or loopback as you say). No way: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever I told you, everything is correct. It never fails me, nor in this position. Everything is alright. So. Why do you think I have something wrong? No way. Thanks. -- Saludos de Santiago José López borrazás.
