June 2021


comitup – Manage wifi connections on headless, unconnected systems


comitup [options]


The comitup service provides a means to establish a connection between a computer and a wifi access point, in the case where wifi is the only means available to access the computer.

On startup, the service will attempt to connect to wifi using established networkmanager(8) connections. If this is not successful, comitup will establish a wifi hotspot with the name comitup-<nnn>, where <nnn> is a persistent number.

While the hotspot is active, a comitup-web(8) service is available to manage connecting to an access point. A captive portal environment is established to aid in discovery of the web service.

If two wifi interfaces are available, the hotspot will remain active on the first interface, and the internet connection will be made on the second. Otherwise, the hotspot will be replaced with the internet connection.

In all states, avahi-daemon(8) is used to publish the mdns host name comitup-<nnn>.local, making the web service accessible as e.g. http://comitup-123.local, for systems supporting Zeroconf. For other systems, a comitup Workstation entry is published which is visible to Zeroconf browsing applications, allowing the IP address to be manually determined. The web service address is

comitup logs to /var/log/comitup.log.


D-Bus Interface

Comitup provides a D-Bus object which claims the name com.github.davesteele.comitup on the path /com/github/davesteele/comitup, supporting the interface com.github.davesteele.comitup. The interface includes the following methods.

Comitup is Copyright (C) 2016-2019 David Steele <>.


comitup-conf(5), comitup-cli(1), comitup-web(8)