zepto-forks/meta-mortsgna
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

dnsmasq: do not start service automatically to fix networkmanager hotspot

Browse Source 
Networkmanager is our first choice for all images. If it sets up a hotspot it
starts dnsmasq and configures it. This breaks if dnsmasq is running as service
and set-up by (default-) configuration:

| dnsmasq-dhcp[361]: no address range available for DHCP request via wlan0

Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
This commit is contained in:
Andreas Müller
2020-08-31 20:15:53 +02:00
parent e010cfc0b1
commit 488534e5b0
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
appends/meta-networking/dnsmasq_%.bbappend Normal file
View File

@@ -0,0 +1,5 @@
# In our environment dnsmasq is used by networkmanager only. That takes care
# of all the configuration parameters necessary. Unfortunately this is broken
# by dnsmasq running as service: It is set-up by configuration files and that
# are not matching networkmanagers's needs.
SYSTEMD_AUTO_ENABLE_${PN} = "disable"