dnsmasq's TFTP does not bind to DHCP'd interfaces

Bug #1682442 reported by Michał Sawicz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dnsmasq (Ubuntu)
New
Undecided
Unassigned

Bug Description

Having enabled tftp in dnsmasq:

 cat /etc/dnsmasq.d/tftp
enable-tftp=lo,em1
tftp-root=/var/tftp

On boot, it only binds on localhost:

 sudo netstat -anp | grep dnsmasq
udp 0 0 127.0.0.1:69 0.0.0.0:* 1946/dnsmasq
udp6 0 0 ::1:69 :::* 1946/dnsmasq

This is likely due to my em1 interface being configured via DHCP, as restarting dnsmasq gets it to bind to it again:

 sudo netstat -anp | grep dnsmasq
udp 0 0 127.0.0.1:69 0.0.0.0:* 12250/dnsmasq
udp 0 0 10.0.1.100:69 0.0.0.0:* 12250/dnsmasq
udp6 0 0 ::1:69 :::* 12250/dnsmasq
udp6 0 0 fe80:::::: :::* 12250/dnsmasq

Should dnsmasq only start after the network got configured? Or do I need to add an explicit dependency in my dnsmasq unit?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq 2.75-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Apr 13 15:50:24 2017
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to xenial on 2016-10-28 (167 days ago)

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :

Hi, I am marking this as a dup of LP: #1531184 as this sounds a lot like the same issue and could be resolved in the same manner. If I have misunderstood or overlooked something please feel free to add details here. Thanks!

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.