Note: It may be a good idea to use systemctl --type=service to ensure that no other service is running that may want to configure the network. Multiple networking services will conflict.
Did you miss this note or just not understand that dhcpcd would be one of the services that would be a problem? You had to enable dhcpcd manually, so you had to have some understanding that it was configuring the network.
]]>I'm confused, did someone prevent you from updating the Wiki?
Yes, I tried, but I admittedly lack the skills to debate technically, with someone who obviously possesses the skills.
https://wiki.archlinux.org/index.php?title=NetworkManager&action=history
(cur | prev) 07:09, 3 September 2013 Lahwaacz (Talk | contribs) . . (28,477 bytes) (-253) . . (Undo revision 274198 by Jeff story (talk) completely covered by the note above removed text)
(cur | prev) 23:18, 2 September 2013 Jeff story (Talk | contribs) . . (28,730 bytes) (+253) . . (clarify and instruct to disable and stop dhcpcd.service)
Honestly though, at this point, your question is no longer important.
What would be cool though is for someone with the expertise on this subject to take notice, figure out exactly what is lacking in the wiki and be willing to contribute the info for the good of the community, which I believe should include the Arch newbs or non coders / programmers.
Then be able to persuade Scimmia and Lahwaacz that in fact, something needs "fixed", even though from their perspective (Linux guru?) there is nothing wrong or missing.
EDIT: Added second name to clarify situation.
]]>Unfortunately, the wiki "[sic]over loards" seem to obviously not want to clarify this common and ongoing issue .......
I'm confused, did someone prevent you from updating the Wiki?
]]>If the solution to this was clearly spelled out in the wiki, which it is obviously not, based on this and many other threads related to this issue, this problem (of documentation) would not continue to surface on the forums and be a problem to users. Not to mention the 1700+ views to this thread.
Unfortunately, the wiki "over loards" seem to obviously not want to clarify this common and ongoing issue .......
Perhaps this will prompt someone knowledgeable and persistent enough within the arch community to fix this issue and stand up the the wiki over lords.
Seems some don't want to include more appropriate, clear and concise instructions in the wiki related to this issue that are comprehend-able to ALL skill levels of Arch users .
]]>You should see dhcpcd.service* as a (more basic) alternative to NetworkManager.service or wicd.service. You should never have two or more of these network managers competing to take control of a network interface.
@salbahis: I doubt that dhcpcd enabled itself. You are in control of your system and you enabled dhcpcd.service* (creating symlinks in the .wants directory).
* or dhcpcd@<interface>.service
]]>So why does having dhcpcd running cause NM not to work? Doesn't NM need it to get an IP address from the router? Hence the "dhcp" parameter in NetworkManager.conf.
This should definitely be in the troubleshooting section of the NM wiki. Mine was a very standard installation, and I ran into this.
Interestingly enough, disabling `dhcpcd` was the solution here.
I was having the same issue with NM and dhcpcd. Now NM works
perfectly -- even logs in to the available wireless network when
the computer boots. I'm still curious about how NM is fetching
the IP address list with dhcpcd disabled.
So why does having dhcpcd running cause NM not to work? Doesn't NM need it to get an IP address from the router? Hence the "dhcp" parameter in NetworkManager.conf.
This should definitely be in the troubleshooting section of the NM wiki. Mine was a very standard installation, and I ran into this.
]]>I think the bigger question though is if you are able to use dhcpcd manually (or dhclient for that matter). Either that, you can test if the dhcpcd@<interface>.service works for you. If those work, then it is a problem with network manager. If not, then you have a larger problem that is independent of any network management program.
]]>$ sudo systemctl disable dhcp-daemon
Failed to issue method call: No such file or directory
$ sudo systemctl disable dhclient
Failed to issue method call: No such file or directory