From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id DF66413838B for ; Mon, 13 Oct 2014 23:57:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 79C08E0A4F; Mon, 13 Oct 2014 23:57:04 +0000 (UTC) Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4A3FBE09F7 for ; Mon, 13 Oct 2014 23:57:03 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id h3so12521085igd.5 for ; Mon, 13 Oct 2014 16:57:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=+DJmqbqlVoB47dx5FRdpYfWoq3PUDqUFImY61Ae6Rwk=; b=cbZhnRz0PMCOPiyrce/BmA3GWT2Tf1Jnh0yk36NsiraW6/R9wg0zFY/nG8Iy6gvqsM 3nPzl8wkL1loksu5Rkgnq6xy8vhNdEGACwX3A0ZQxIY6OxiTLLtopdiwvEB3ilPTpuXu QTyFV3hcWLwEZK6FE4R3RnHpvpKfsAkdkd5aaq+Q2aPay8YOF3lffzC+mmBRwGzEvOs+ 5r4t63Og1VHTqOLV57vPDHRynbIRC0+9YG0B+Dpmkyh99NWfubROX8GIrfOuZ+GiwveE 7Vw9coXpW5ZplVexOMeQqeFFrJP7DgB1BNJOdglTHxXbrDHg1ac2PSdUF+CWOarjOXWs 5+RA== X-Received: by 10.42.100.14 with SMTP id y14mr1772721icn.64.1413244622511; Mon, 13 Oct 2014 16:57:02 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.148.19 with HTTP; Mon, 13 Oct 2014 16:56:42 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Mon, 13 Oct 2014 18:56:42 -0500 Message-ID: Subject: Re: [gentoo-user] [systemd] Is this a NetworkManager bug? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 210a954c-4921-4c69-8a9b-5e7863cfbf06 X-Archives-Hash: 8de08da733d519bf1d40e67c714e7e58 On Mon, Oct 13, 2014 at 6:39 PM, walt wrote: > I just switched my home LAN from wired to all wifi and I'm having trouble > with NetworkManager at boot time. > > I have systemd start NetworkManager at boot because I need the internet > for ntpdate and to start the nfs server for the LAN. Before I switched > to all-wireless this method worked perfectly, but no longer. > > After bootup I see that NetworkManager started wpa_supplicant in the > background, but apparently does *not* run dhcpcd. (The wlan0 is up > but it has no IP address and the routing table is empty.) Do you have a system-wide connection for the wireless network? They live in /etc/NetworkManager/system-connections. Also, what does "nmcli -p general" says? In my case is: centurion ~ # nmcli -p general =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D NetworkManager status =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN ------------------------------------------------------------- connected full enabled enabled enabled enabled > As an alternative to NetworkManager I can have systemd start dhcpcd > at boot, which almost (but not quite) works well enough. This > causes a race condition because wlan0 takes several seconds to come > up properly and by then both ntpdate and nfs-server have already > run and failed. > > So, I asked myself, why not have systemd start dhcpcd at boot in > addition to NetworkManager? NetworkManager starts wpa_supplicant, but it does *NOT* use wpa_supplicant.conf. If you do systemctl status wpa_supplicant.service you will see that wpa_supplicant runs with the "-u" flag; that enables the DBus control interface, and it's through this that NetworkManager controls wpa_supplicant. If you do not have system-wide connections, NM will ask wpa_supplicant to *not* enable any connection. NM calls the shots in this case. > The reason that fails is that they both start wpa_supplicant in > the background and the two instances interfere with each other. > > Anyone see a way around this catch22? If I'm not mistaken, you need a system-wide NM connection enabled. You can use nm-connection-editor (included with nm-applet), or nmtui (ncurses interface since 0.9.10.0). Also, and orthogonal to almost all of this; I switched from ntp to systemd-timesyncd, and it works *great*, specially in my laptop. With my laptop, changing networks all the time, ntpd never quite worked. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico