CONNMAN(8)

💖 CONNMAN 💖

okay bestie, gather round, because we're talking about ConnMan — the network management daemon, and honestly? she's that girl. this page lives in section 8 of the manual (System Manager's Manual), so yes, she's a system-level queen. 👑

---

✨ NAME ✨

ConnMan — network management daemon. that's it, that's the whole vibe. no cap.

---

🎀 SYNOPSIS 🎀

connmand [--version|--help]

connmand [-c file] [-d [file[,...]]] [-i interface[,...]] [-I
interface[,...]] [-W driver[,...]] [-p plugin[,...]] [-P plugin[,...]]
[-n] [-r]

so basically there's a "just tell me the version or help me" mode and a "okay let's actually configure every single thing" mode. both valid. both iconic. 💅

---

🦋 DESCRIPTION 🦋

ConnMan is a daemon for managing internet connections inside devices running the Linux operating system. she's built to be slim and to use as few resources as possible — low maintenance, high performance, the dream honestly.

she's a fully modular system, which means you can extend her through plug-ins to support literally all kinds of wired or wireless technologies. 🌈 and get this — configuration methods like DHCP and domain name resolving? also implemented as plug-ins. the plug-in approach means she's super easy to adapt and modify for whatever use case you've got going on. versatile queen. ✨

---

🌸 OPTIONS 🌸

the following options are supported, and yes, we're going through all of them, no skipping:

• -v, --version — prints the ConnMan software version and then dips. exit stage left. 👋
• -h, --help — prints ConnMan's available options and exits. your little cheat sheet moment.
• *-c *file, --config=file — specify a configuration file to set up various settings for ConnMan. if you don't specify one, the default value /etc/connman/main.conf is used. see connman.conf(5) for more tea on the configuration file. using a config file is totally optional, and sane default values are used if the config file is missing. she'll cope either way bestie. 🫶
• -d [file[,...]], --debug[=file[,...]] — sets how much information ConnMan sends to the log destination (usually syslog's daemon facility). if the file options are omitted, then debugging information from all the source files gets printed. if file options are present, then only debug prints from that source file get printed. example:

connmand --debug=src/service.c,plugins/wifi.c

• *-i *interface[,...], --device=interface[,...] — only manage these network interfaces. by default, all network interfaces are managed. so this is the "okay but only these ones" option.
• *-I *interface[,...], --nodevice=interface[,...] — never manage these network interfaces. and plot twist: this option can be a pattern containing * and ? characters. wildcard slay. ✨
• *-p *plugin[,...], --plugin=plugin[,...] — load these plugins only. this option can also be a pattern containing * and ? characters.
• *-P *plugin[,...], --noplugin=plugin[,...] — never load these plugins. yep, you guessed it, this one can be a pattern containing * and ? characters too. consistency is beautiful.
• *-W *driver[,...], --wifi=driver[,...] — the wifi driver that WiFi/Supplicant should use. if this flag is omitted, then the value nl80211,wext is used by default. 💅
• -n, --nobacktrace — don't print out backtrace information. sometimes you just don't wanna see all that, and that's valid.
• -n, --nodaemon — do not daemonize. this is useful for debugging, and it directs log output to the controlling terminal in addition to syslog. (yes, both of these use -n. the manpage said it, not me. 🙈)

okay so about that double -n — both --nobacktrace and --nodaemon are listed with -n in the original. that's exactly what it says, so that's exactly what you're getting. choose wisely, or use the long form, bestie. 😭

• -r, --nodnsproxy — do not act as a DNS proxy or support external DNS resolving. depending on how ConnMan is compiled, she will by default either direct all DNS traffic to herself by setting nameserver to 127.0.0.1 in the resolv.conf(5) file, or leave DNS management to an external entity, such as systemd-resolved. if that's not what you want, and you want all programs to call directly some DNS server, then you can use the --nodnsproxy option. ConnMan then figures out the DNS server and search domain on startup and sets them in resolv.conf(5).

heads up though — if this option is used, then ConnMan is not able to cache the DNS queries, because the DNS traffic is not going through ConnMan, and that can cause some extra network traffic. so like, tradeoffs. it's giving "convenience costs bandwidth". 💀

---

💜 SEE ALSO 💜

go read these next, they're all part of the extended universe:

• connmanctl(1)
• connman.conf(5)
• connman-service.config(5)
• connman-vpn(8)

---

and that's the whole page bestie!! 🎀 this version of the manual is dated 2015-10-15 and comes from the System Manager's Manual source. so if you ever forget any of this, just pull up CONNMAN(8) again. iykyk. 💖✨🦋🌸👑