Re: NetworkManager "nmcli device" saying eth0 and wlan0 are "unavailable"
"Rainer Fiebig" ([email protected] via blfs-support Mailing List) <[email protected]> Mon, 27 Apr 2026 11:39:15 +0200
| Newsgroups | gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1777282780-1253-26628 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Am 27.04.26 um 06:06 schrieb Subhrajit Sain ([email protected] via blfs-support Mailing List): > Hello Rainer, > > I have renamed the config file to no-dns-update.conf.bak. But my resolv.conf is set to read only anyways. So that will not change anything. I tried and it still gave the network unreachable message from ping. You said: "The same devices work as usual with wpa_supplicant and dhcpcd via init scripts." So your network-setup seems to be basically OK. But your NetworkManager-configuration probably is not or is not suitable for how you have set up your network. See whether the logs offer any clues, like with ~> less /var/log/sys.log | grep -i 'networkmanager' And meticulously check whether your network- and NetworkManager-setup deviates from the books. I doubt that a read-only /etc/resolv.conf makes sense with NetworkManager, as NM tries to automatically configure your network for you. As I understand it, that's the whole point about NM. But anyway - here are the permissions for that file on my systems: ~> ls -l /etc/resolv.conf -rw-r--r-- 1 root root 30 27. Apr 10:02 /etc/resolv.conf And here's the first line in that file and in that of an old Debian 8 with NM: ~> head -n1 /etc/resolv.conf # Generated by NetworkManager HTH and good luck! Rainer ------------=_1777282780-1253-26628 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- http://lists.linuxfromscratch.org/sympa/info/blfs-support Unsubscribe: See the above information page ------------=_1777282780-1253-26628--