Difference between revisions of "Talk:NetworkManager"

From ArchWiki
Jump to: navigation, search
m (Remove closed discussions.)
(Add recommendation to install dhclient)
 
(36 intermediate revisions by 14 users not shown)
Line 1: Line 1:
== GNOME 3 and nm-applet ==
+
== Add recommendation to install dhclient ==
  
Looks like GNOME 3 doesn't need nm-applet any more. Moreover, it competes with the shell's network agent for new connections. Does anyone copy this? Should this be mentioned on the page?
+
NetworkManager tries to use dhclient by default but falls back to dhcpcd if dhclient is not installed.
 +
 
 +
However, if NetworkManager uses dhcpcd, NetworkManager does not terminate dhcpcd when systemd tells NetworkManager to shut down. See [https://mailman.archlinux.org/pipermail/arch-general/2014-April/035827.html this mailing list thread].
 +
 
 +
I wanted to suggest some ideas here before making any drastic changes.
 +
 
 +
I think there should be a recommendation to install dhclient in the "Base install" section, above "VPN support". Installing dhclient is preferred because it plays nicely with NetworkManager. Also, dhclient requires no configuration for NetworkManager to use it.
 +
 
 +
If adding a recommendation in the "Base install" section is too much, I would at least like to add this issue to the troubleshooting section so others are not baffled by NetworkManager leaving dhcpcd running.
 +
 
 +
[[User:KlipperKyle|KlipperKyle]] ([[User talk:KlipperKyle|talk]]) 03:54, 10 April 2014 (UTC)
 +
 
 +
:The behaviour is obviously intentional as per the provided systemd unit:
 +
{{hc|/usr/lib/systemd/system/NetworkManager.service|2=
 +
...
 +
# NM doesn't want systemd to kill its children for it
 +
KillMode=process
 +
}}
 +
:Ideally this problem would be resolved in the NetworkManager itself, feel free to submit a bug.
 +
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:28, 10 April 2014 (UTC)
 +
 
 +
::Thanks, Lahwaacz. It appears the NetworkManager team already knows about the dhcpcd issue ([https://bugzilla.gnome.org/show_bug.cgi?id=723746 Bug 723746]).
 +
::Also, after more poking around it appears that dhclient is left running after stopping NetworkManager. However, NetworkManager actually restarts dhclient when NetworkManager starts up. (NetworkManager does not restart dhcpcd when initializing.)
 +
::Shall I add a section about dhcpcd not properly restarting to the troubleshooting section?
 +
::[[User:KlipperKyle|KlipperKyle]] ([[User talk:KlipperKyle|talk]]) 02:20, 12 April 2014 (UTC)
 +
 
 +
:::Adding a note to our wiki will not help to resolve the real problem - please add comments to the upstream bug report you referenced. They are missing the detail about {{ic|KillMode}} in systemd unit.
 +
:::Additionally, could you test if resetting {{ic|KillMode}} back to default {{ic|control-group}} actually works? I.e. create the following file:
 +
{{hc|/etc/systemd/system/NetworkManager.service.d/killmode.conf|<nowiki>
 +
[Service]
 +
KillMode=control-group
 +
</nowiki>}}
 +
:::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:06, 12 April 2014 (UTC)
 +
[[User:0xdelta|0xdelta]] ([[User talk:0xdelta|talk]]) 07:52, 10 July 2016 (UTC)
 +
: I'm sorry to bump such an old thread, but there are still some issues with NetworkManager and dhcpcd: At university we use the "eduroam" wireless network. To make things short, I could not connect to the internet via NetworkManager/dhcpcd, but using the console worked. Finally I installed dhclient and edited the NetworkManager config to use dhclient, and that solved my problem. But that took some hours for me to find out (I'm kind of a newbie). It would be nice to mention that workaround in the Troubleshooting section, what do you think?
 +
 
 +
:: NetworkManager with dhcpcd didn't work because {{Pkg|networkmanager}} is built without dhcpcd support [https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/networkmanager&id=a1df79cbcebaec0c043789eb31965e57d17b6cdb]. AFAIK it's recommended to use {{ic|1=dhcp=internal}}. ––&#160;[[User:Nl6720|<span style="font-family:serif; font-weight:bold; color:#800080;">nl6720</span>]]&#8239;[[User talk:Nl6720|<span style="color:#808080; vertical-align:super; font-size:smaller; font-weight:lighter;">talk</span>]] 08:15, 10 July 2016 (UTC)
 +
 
 +
:: You're right. But even the internal dhcp client wouldn't work with eduroam. It always timed out after 45 seconds. [[User:0xdelta|0xdelta]] ([[User talk:0xdelta|talk]]) 08:22, 10 July 2016 (UTC)

Latest revision as of 08:22, 10 July 2016

Add recommendation to install dhclient

NetworkManager tries to use dhclient by default but falls back to dhcpcd if dhclient is not installed.

However, if NetworkManager uses dhcpcd, NetworkManager does not terminate dhcpcd when systemd tells NetworkManager to shut down. See this mailing list thread.

I wanted to suggest some ideas here before making any drastic changes.

I think there should be a recommendation to install dhclient in the "Base install" section, above "VPN support". Installing dhclient is preferred because it plays nicely with NetworkManager. Also, dhclient requires no configuration for NetworkManager to use it.

If adding a recommendation in the "Base install" section is too much, I would at least like to add this issue to the troubleshooting section so others are not baffled by NetworkManager leaving dhcpcd running.

KlipperKyle (talk) 03:54, 10 April 2014 (UTC)

The behaviour is obviously intentional as per the provided systemd unit:
/usr/lib/systemd/system/NetworkManager.service
...
# NM doesn't want systemd to kill its children for it
KillMode=process
Ideally this problem would be resolved in the NetworkManager itself, feel free to submit a bug.
-- Lahwaacz (talk) 06:28, 10 April 2014 (UTC)
Thanks, Lahwaacz. It appears the NetworkManager team already knows about the dhcpcd issue (Bug 723746).
Also, after more poking around it appears that dhclient is left running after stopping NetworkManager. However, NetworkManager actually restarts dhclient when NetworkManager starts up. (NetworkManager does not restart dhcpcd when initializing.)
Shall I add a section about dhcpcd not properly restarting to the troubleshooting section?
KlipperKyle (talk) 02:20, 12 April 2014 (UTC)
Adding a note to our wiki will not help to resolve the real problem - please add comments to the upstream bug report you referenced. They are missing the detail about KillMode in systemd unit.
Additionally, could you test if resetting KillMode back to default control-group actually works? I.e. create the following file:
/etc/systemd/system/NetworkManager.service.d/killmode.conf
[Service]
KillMode=control-group
-- Lahwaacz (talk) 09:06, 12 April 2014 (UTC)

0xdelta (talk) 07:52, 10 July 2016 (UTC)

I'm sorry to bump such an old thread, but there are still some issues with NetworkManager and dhcpcd: At university we use the "eduroam" wireless network. To make things short, I could not connect to the internet via NetworkManager/dhcpcd, but using the console worked. Finally I installed dhclient and edited the NetworkManager config to use dhclient, and that solved my problem. But that took some hours for me to find out (I'm kind of a newbie). It would be nice to mention that workaround in the Troubleshooting section, what do you think?
NetworkManager with dhcpcd didn't work because networkmanager is built without dhcpcd support [1]. AFAIK it's recommended to use dhcp=internal. –– nl6720talk 08:15, 10 July 2016 (UTC)
You're right. But even the internal dhcp client wouldn't work with eduroam. It always timed out after 45 seconds. 0xdelta (talk) 08:22, 10 July 2016 (UTC)