Public bug reported:
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)
** Affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1682442
Title:
dnsmasq's TFTP does not bind to DHCP'd interfaces
Status in dnsmasq package in Ubuntu:
New
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682442/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
