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 43E261387CA for ; Wed, 15 Oct 2014 12:41:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5A876E0983; Wed, 15 Oct 2014 12:41:12 +0000 (UTC) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5A347E0967 for ; Wed, 15 Oct 2014 12:41:10 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id w7so924664lbi.8 for ; Wed, 15 Oct 2014 05:41:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=l7904LFuWazavPmJLdiiN2Cex80qoKrZTFOm/MNWoMw=; b=DUXoD2yidq51Kptr2su0mNG3YuekVGSXlXuGVQQHjKpivIUxjOlBMkW1pzKBeXhWAN fuGFhEhp+EpLzC9XnwGYfZxeha0k839+laOXZPhGG1MZg4ZsRNKbAP9lmERKxUIFRRXs 0DHwo/ywR1jMok9RbXoO0EYu84AOFI2ACLh9jD+LBYnm5E0Ifqzl1i7sFTGSbppDgqWY 55mSIxQlXnLoQK1Z05T0lVs7CgCzhWLhuxF5MIo8xtPWZsZUItexBTwoIDfWqWXuHpXH CBqq9xnPLoxWT1pKFdeLNyRoJ5TzTJIDhVzC/EYvumDjW92zxuxhJoT8flhhUIS3XiCu AyKA== 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 X-Received: by 10.112.135.197 with SMTP id pu5mr12108374lbb.22.1413376868711; Wed, 15 Oct 2014 05:41:08 -0700 (PDT) Received: by 10.112.77.166 with HTTP; Wed, 15 Oct 2014 05:41:08 -0700 (PDT) In-Reply-To: References: Date: Wed, 15 Oct 2014 06:41:08 -0600 Message-ID: Subject: Re: [gentoo-user] Re: [systemd] Is this a NetworkManager bug? From: =?UTF-8?Q?Jc_Garc=C3=ADa?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 3e0e73e4-4832-4de2-b1fe-0acc253b9495 X-Archives-Hash: 35d653e3eb7a733d458415987d7eec3a 2014-10-14 16:54 GMT-06:00 Canek Pel=C3=A1ez Vald=C3=A9s = : > On Tue, Oct 14, 2014 at 5:48 PM, walt wrote: > [ snip ] >> Lots of great information, thanks. What I learned while following up >> on your hints is that the NM behavior I thought was a bug is merely >> a feature ;) >> >> After boot, but before startx, wlan0 exists but is not properly set >> up. After X is running I can use the nm-applet to click on the name >> of my wireless network and *then* NM runs dhcpcd to configure wlan0 >> and set up the routing table. It works, but I need to do that manually >> after every boot, not really optimal for my purpose. > I had this problem, but, with a Ethernet connection, I wanted NM to connect it via dhcp at boot, but didn't happen, and the same as you, once logged-in just 2 clicks and the connection worked, after digging a little the configs, I found, somehow this line got into my /etc/NetworkManager/NetworkManager.conf no-auto-default=3Dp2p1 I removed that and now It works as it should, maybe something like this is your problem. > I've seen this behavior before (that you need to manually "enable" the > wireless connection), but never on my machines. On my two wireless > systems (laptop and desktop), NM enables the connection by default. I > don't think I did anything special for this to happen, it just does. > >> I tried Neil's suggestion to use systemd-networkd and it works perfectly >> for this (desktop) machine. (BTW enabling systemd-networkd also pulls >> in systemd-timesyncd, which works great, just as you said.) > > Good to know. > > Regards. > -- > Canek Pel=C3=A1ez Vald=C3=A9s > Profesor de asignatura, Facultad de Ciencias > Universidad Nacional Aut=C3=B3noma de M=C3=A9xico >