dnsmasq is started with a --cache-size=0 argument, not overridable

Bug #1566795 reported by Marius Nuennerich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

dnsmasq is started with --cache-size=0 as commandline argument by NetworkManager; this a hard coded setting making it impossible to override per config file.

$ ps auxww | grep dnsmasq
nobody 5375 0.0 0.0 54488 4452 ? S Apr05 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d

Could somebody please move this option (and maybe others) to a config file?
I would like to add some local caching. No, I don't have security concerns, I'm the only user of this machine.

$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 6 12:10:01 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-13 (52 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160213)
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto static metric 100
 169.254.0.0/16 dev enp2s0 scope link metric 1000
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.14 metric 100
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
 virbr0 801e8478-6dad-4d21-ac62-443b5e8c3043 bridge 1459940763 2016-04-06T12:06:03 IST no 0 no /org/freedesktop/NetworkManager/Settings/1 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/0
 Kabelnetzwerkverbindung 1 71917d5e-62b5-417e-9a6d-f8c31a8e0e1f 802-3-ethernet 1459940763 2016-04-06T12:06:03 IST yes 0 no /org/freedesktop/NetworkManager/Settings/0 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 virbr0 bridge connected /org/freedesktop/NetworkManager/Devices/1 virbr0 801e8478-6dad-4d21-ac62-443b5e8c3043 /org/freedesktop/NetworkManager/ActiveConnection/0
 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 71917d5e-62b5-417e-9a6d-f8c31a8e0e1f /org/freedesktop/NetworkManager/ActiveConnection/2
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
 virbr0-nic tap unmanaged /org/freedesktop/NetworkManager/Devices/3 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Marius Nuennerich (mwrius) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.