Closed mstormi closed 3 years ago
Try those edits. The files are in /usr/share/comitup/dns/.
Thanks for your fast response. However, turns out that whole "dns" directory does not exist on my box . I did not use the image but manually installed the package - would it need to nonetheless exist ? I'm using the comitup package from and on top of latest (Aug 2020 image) Raspi OS, v1.3.1-1 according to dpkg -s but frankly I don't know for sure what comitup version is contained and comitup seems not to have a -version switch (so how can I find out ?) The dnsmasq binary from the dnsmasq-base package was installed (but the dnsmasq package or service dnsmasq are not. When I added them the dnsmasq.service refused to start because of port 53 in use, the dnsmasq binary started by comitup occupying it). Note installing the comitup package has dependencies upon network-manager which gets installed, too.
So that does not solve my problem. [ but as a sidenote, this might or might not explain why the --interface option is apparently insufficient so eventually your fix is not needed (although I guess it doesn't harm to leave it in). ]
For the version:
"dpkg --list comitup"
For the location of the config files in your setup:
"dpkg --listfiles comitup"
There are a couple of ways to stay with more recent versions. Use the Comitup spin, or add the Comitup Repository.
The version in Buster, 1.3.1-1, is 2 years old. There have been many, many releases since then (1.13-4 is current).
oh ok. Got 1.13 working fine now. Apologies I didn't check before raising this issue. Thanks for your support.
Apparently comitup serves dhcp on the interfaces it works on. Makes sense for Wifi but for Ethernet ? I had a comitup box connected via LAN, too, and it messed up my home network overruling my regular DHCP server Had a power outage with everything booting again and some of my clients connected to the comitup box which is definitely not desired (in probably no use case whatsoever) so can you disable serving DHCP to Ethernet please ?