Hello, thanks for fast answer and suggestions.
>1) General is the wrong package for this bug. (i assume it's going to
get closed, network-manager or ifupdown are probably a better idea).
I don't know which one and I'm not sure if it is not somethink else. I
haven't found anything like this in bugzilla/google.
>2) Assuming the former is causing the problem (because you have eth0
in /etc/network/interfaces).
I have only "auto lo" in /etc/network/interfaces
>FIX 1) Set managed=true in /etc/NetworkManager/NetworkManager.conf. as
per https://wiki.debian.org/NetworkManager#Enabling_Interface_Management
(and restart)
This doesn't change anything
>FIX 2) If that fails (and you use network-manager) remove ALL
instances of eth0 in /etc/network/interfaces (and restart) Expect this
bug to be closed.
There are no eth0 "lines" in /etc/network/interfaces
>Check network-manager bugs in the bug tracker. And at some point plan
a project to change the internal IP range. 169.254.x.x is wrong.
I know... this was set here many years ago. Its difficult (people
remember addresses, the configuration of printers and such staff).
Regards,
Maciek
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54873037.6090...@ibb.waw.pl
