David Steele
David Steele
Your logs suggest you may be running a pretty old version of Comitup - the one included in Ubuntu 22.04. Current is 1.37-1. Consider the [repo](https://davesteele.github.io/comitup/ppa.html). Note that I incorrectly...
If the service crashes/restarts, the comitup-cli connection is lost, and has to be restarted. It's not intended behavior, but I don't know what is going on right now.
Start by finding any tracebacks in e.g. daemon.log, or run in the terminal, with possibly debug-level logs.
... or add another USB WiFi adapter. Comitup will make use of it to do the scan. Be sure to set [*enable_appliance_mode*](https://davesteele.github.io/comitup/man/comitup-conf.pdf) according to your wishes.
I had not included arm64 in the repository. Try it again, and tell me how it works.
I haven't looked into that yet.
If the Ethernet connection has an upstream connection and is using DHCP, then it will configure to use that when connected.
Note that this capability is part of the Comitup image, not the package itself.
The current DNS behavior is key to make the captive portal work. Changing the DNS IP would break that. You probably would be interested in the proposed enhancement in https://github.com/davesteele/comitup/issues/168
Upon reflection, there are multiple strategies for implementing the captive portal - both defined in dns-hotspot.conf. Option 160 explicitly defines a captive portal url. Option 6 defines a dns server...