Connection Manager簡稱connman

ConnMan

   Connection Manager簡稱connman，connman是使用d-bus做為進程間通信機制來管理 Linux網絡鏈接的一種軟件。在connman的d-bus接口中，有一個接口叫做service。該接口的全稱為：net.connman.Service，自然是掛在net.connman上面的。做為net.connman.Service接口，它可以訪問到network的細節以及用戶偏好使用什么類型的網絡（比如3g、wifi、wimax等等）。外部的程序就通過net.connman.Service的一堆Properties和Methods來實現它基本的功能。（可能詮釋的不對，可能是整體的connman的功能）
        核心的邏輯如下：connman維護一個 信號標記並且將所有可能連接上的網絡服務建成一個列表（分類成普通網絡、用戶喜歡的以及上次使用的網絡）。做為網絡服務，它可以是以太網設備，WIFI，WIMAX，或者是遠程藍牙設備（比如手機）。

        這個列表的分類和排序是由connman內部實現，沒必要由使用它的用戶來決定怎么去將網絡排序之類的。用戶的決定（比如鏈接WIFI、關閉以太網等等）會通過connman實現，與此同時connman會重新對列表中的網絡服務進行排序。

Related articles

• Network configuration
• Wireless network configuration
• Category:Network configuration

ConnMan is a command-line network manager designed for use with embedded devices and fast resolve times. It is modular through a plugin architecture, but has native DHCP and NTP support.

Contents

• 1 Installation
  • 1.1 Desktop clients
• 2 Usage
  • 2.1 Wired
  • 2.2 Wi-Fi
    • 2.2.1 Enabling and disabling wifi
    • 2.2.2 Connecting to an open access point
    • 2.2.3 Connecting to a protected access point
  • 2.3 Settings
  • 2.4 Technologies
• 3 Tips and tricks
  • 3.1 Avoid changing the hostname
  • 3.2 Prefer ethernet to wireless
  • 3.3 Exclusive connection
  • 3.4 Connecting to eduroam (802.1X)
  • 3.5 Avoiding conflicts with local DNS server
  • 3.6 Blacklist interfaces
• 4 Troubleshooting
  • 4.1 Error /net/connman/technology/wifi: Not supported
  • 4.2 Error /net/connman/technology/wifi: No carrier
  • 4.3 Error Failed to set hostname/domainname
  • 4.4 Unknown route on connection
• 5 See also

Installation

Install the connman package. wpa_supplicant and bluez are optional dependencies required for Wi-Fi and Bluetooth functionality respectively.

Before enabling connman.service, ensure any existing network configuration is disabled.

Desktop clients

• cmst — Qt GUI for ConnMan.

https://github.com/andrew-bibb/cmst || cmst^AUR

• connman-ncurses — Simple ncurses UI for ConnMan; not all of connman functionality is implemented, but usable (with X or from terminal without X), see the wiki.

https://github.com/eurogiciel-oss/connman-json-client || connman-ncurses-git^AUR

• connman-notify — Connman event notification client

https://github.com/wavexx/connman-notify || connman-notify^{AUR[broken link: archived in aur-mirror]}

• ConnMan-UI — GTK3 client applet.

https://github.com/tbursztyka/connman-ui || connman-ui-git^AUR

• connman_dmenu — Client/frontend for dmenu.

https://github.com/taylorchu/connman_dmenu || connman_dmenu-git^AUR

• Econnman — Enlightenment desktop panel applet.

http://www.enlightenment.org || econnman^AUR

• LXQt-Connman-Applet — LXQt desktop panel applet.

https://github.com/surlykke/lxqt-connman-applet || lxqt-connman-applet-git^AUR

• qconnman-ui — Qt management interface used on O.S. Systems products

https://github.com/OSSystems/qconnman-ui || qconnman-ui-git^{AUR[broken link: archived in aur-mirror]}

• connman-gtk — GTK client.

https://github.com/jgke/connman-gtk || connman-gtk^AUR

• gnome-extension-connman — Gnome3 extension for connman; it contains only some of the functionality without installing connman-gtk.

https://github.com/jgke/gnome-extension-connman || https://extensions.gnome.org/extension/981/connman-extension/

Usage

This article or section needs expansion.

Reason: Only Wired and Wi-Fi plugins are described. (Discuss in Talk:ConnMan#)

ConnMan has a standard command line client connmanctl. It can run in 2 modes:

• In command mode commands are entered as arguments to connmanctl command, just like systemctl.
• Interactive mode is started by typing connmanctl without arguments. Prompt will change to connmanctl> to indicate it is waiting for user commands, just like python interactive mode. The interactive mode supports tab completion, which makes finding the correct connection easy.

Wired

ConnMan will automatically handle wired connections.

Wi-Fi

Enabling and disabling wifi

To check if wifi is enabled you can run connmanctl technologies and check for the line that says Powered: True/False. To power the wifi on you can run connmanctl enable wifi or if you need to disable it you can run connmanctl disable wifi. Other ways to enable wifi could include using the Fn keys on the laptop to turn it on or running ip link set <interface> up.

Connecting to an open access point

The commands in this section show how to run connmanctl in command mode.

To scan the network connmanctl accepts simple names called technologies. To scan for nearby Wi-Fi networks:

$ connmanctl scan wifi

To list the available networks found after a scan run (example output):

$ connmanctl services

*AO MyNetwork               wifi_dc85de828967_68756773616d_managed_psk
    OtherNET                wifi_dc85de828967_38303944616e69656c73_managed_psk 
    AnotherOne              wifi_dc85de828967_3257495245363836_managed_wep
    FourthNetwork           wifi_dc85de828967_4d7572706879_managed_wep
    AnOpenNetwork           wifi_dc85de828967_4d6568657272696e_managed_none

To connect to an open network, use the second field beginning with wifi_:

$ connmanctl connect wifi_dc85de828967_4d6568657272696e_managed_none

Tip: Network names can be tab-completed.

You should now be connected to the network. Check using ip addr or connmanctl state.

Connecting to a protected access point

For protected access points you will need to provide some information to the ConnMan daemon, at the very least a password or a passphrase.

The commands in this section show how to run connmanctl in interactive mode, it is required for running the agent command. To start interactive mode simply type:

$ connmanctl

You then proceed almost as above, first scan for any Wi-Fi technologies:

connmanctl> scan wifi

To list services:

connmanctl> services

Now you need to register the agent to handle user requests. The command is:

connmanctl> agent on

You now need to connect to one of the protected services. To do this easily, just use tab completion for the wifi_ service. If you were connecting to OtherNET in the example above you would type:

connmanctl> connect wifi_dc85de828967_38303944616e69656c73_managed_psk

The agent will then ask you to provide any information the daemon needs to complete the connection. The information requested will vary depending on the type of network you are connecting to. The agent will also print additional data about the information it needs as shown in the example below.

Agent RequestInput wifi_dc85de828967_38303944616e69656c73_managed_psk
  Passphrase = [ Type=psk, Requirement=mandatory ]
  Passphrase?  

Provide the information requested, in this example the passphrase, and then type:

connmanctl> quit

If the information you provided is correct you should now be connected to the protected access point.

Settings

Settings and profiles are automatically created for networks the user connects to often. They contain fields for the passphrase, essid and other information. Profile settings are stored in directories under /var/lib/connman/ by their service name. To view all network profiles run this command from root shell:

# cat /var/lib/connman/*/settings

Note: VPN settings can be found in /var/lib/connman-vpn/.

Technologies

Various hardware interfaces are referred to as Technologies by ConnMan.

To list available technologies run:

$ connmanctl technologies

To get just the types by their name one can use this one liner:

$ connmanctl technologies | awk '/Type/ { print $NF }'

Note: The field Type = tech_name provides the technology type used with connmanctl commands

To interact with them one must refer to the technology by type. Technologies can be toggled on/off with:

$ connmanctl enable technology_type

and:

$ connmanctl disable technology_type

For example to toggle off wifi:

$ connmanctl disable wifi

Warning: connman grabs rfkill events. It is most likely impossible to use rfkill or bluetoothctl to (un)block devices, yet hardware keys may still work. [1] Always use connmanctl enable|disable