Re: [gentoo-user] Re: [systemd] Is this a NetworkManager bug?

[Jc García]

2014-10-14 16:54 GMT-06:00 Canek Peláez Valdés <caneko@×××××.com>:
> On Tue, Oct 14, 2014 at 5:48 PM, walt <w41ter@×××××.com> 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=p2p1
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áez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
>