Um, if you have pi-hole on that system you're using it for DNS, right? Presumably you are installing dnsmasq to use it as a DHCP server?
If so, the log you posted shows that NetworkManager is starting its own "internal" dnsmasq to be the DHCP server, which means that you have ipv4.method set to 'shared' on wlan0. In this mode, the WiFi IP address is fixed at 10.42.0.1, and the internal dnsmasq server provides DHCP addresses for systems connecting to the hotspot.
If you want to use an external DHCP server (dnsmasq in your case?) set ipv4.method 'manual' on wlan0, and also provide an IP address for it with `ipv4.addresses'
If the above doesn't make sense to you or isn't what you want to do, then would be good for you to explain in sufficient detail how you are thinking about DNS and DHCP servers on this system.
If so, the log you posted shows that NetworkManager is starting its own "internal" dnsmasq to be the DHCP server, which means that you have ipv4.method set to 'shared' on wlan0. In this mode, the WiFi IP address is fixed at 10.42.0.1, and the internal dnsmasq server provides DHCP addresses for systems connecting to the hotspot.
If you want to use an external DHCP server (dnsmasq in your case?) set ipv4.method 'manual' on wlan0, and also provide an IP address for it with `ipv4.addresses'
If the above doesn't make sense to you or isn't what you want to do, then would be good for you to explain in sufficient detail how you are thinking about DNS and DHCP servers on this system.
Statistics: Posted by bls — Wed Aug 28, 2024 1:01 am