FS#39046 - [networkmanager] Ad hoc and AP-mode network doesn't work in Arch Linux without tweaks

Attached to Project: Arch Linux
Opened by Kenni Lund (Kenni) - Tuesday, 25 February 2014, 22:04 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 13 May 2015, 21:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I tried to create an ad hoc network for sharing the internet connection using the NetworkManger "nm-applet" GUI. I ran into two issues, which prevented the configuration to work out-of-the-box in Arch Linux. When the ad hoc network had been created in NetworkManager, I tried to "connect" to the ad hoc network in nm-applet in order to activate the network. At this point NetworkManager failed to connect without any useful GUI error message.

-----

Issue 1:
Looking at the NetworkManager logs with journalctl revealed the following error message:

Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.

I identified this commit from upstream, where the dispatcher gets it own service:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=06a415d9ea2d3155ffa7bdfed999191f31f1f9ef

This service isn't enabled in Arch Linux so running the following two commands solved issue 1:
systemctl enable NetworkManager-dispatcher.service
systemctl start NetworkManager-dispatcher.service

-----

Solution to issue 1: Enable the NetworkManager-dispatcher service by default.

-----

Issue 2:
NetworkManager still wasn't able to start the ad hoc network, but the logs revealed the following error message:

NetworkManager[369]: <error> [1393361692.286352] [nm-device.c:3355] start_sharing(): (wlan0/wlan0): failed to start dnsmasq: Could not find dnsmasq binary.

This was of course solved by installing the "dnsmasq" package.

-----

Solution to issue 2: Add dnsmasq as a required dependency for networkmanager. I understand if this isn't going to happen, as it would logically require the other optional packages (bluez, etc) to become required as well. It would however make NetworkManager more user friendly.

-----

Steps to reproduce:

nm-applet -> Manage connections -> Add.. -> Shared -> (System connection) -> Ok.
Connect to the new network named "Shared_Wireless_Connection" -> Connection fails.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 13 May 2015, 21:01 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 22:25 GMT
Issue 1: Add this information to the Wiki and be done with it. If you really think NetworkManager-dispatcher service should be automatically enabled when you enable NM, talk to upstream; the service files come from them.

Issue 2: dnsmasq is already an optional dep.
Comment by Matthias Dienstbier (fs4000) - Tuesday, 25 February 2014, 22:47 GMT
Issue 1 is already fixed [1], but the old installations have to be fixed manually. So perhaps interesting for the Wiki.

Issue 2: Arch Linux is not about user friendliness. Dnsmasq is not a strict dependency to NetworkManager. Most people won't need it, all the others need to be able to read the optional dependencies.

[1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=75c64763f6b943ab93ebe68a38236c764051f3db

Loading...