dnsmasq bad hex constant with 2 mac addresses but not true

[Dash]

Following line of dnsmasq.conf will not allow dnsmasq to start giving error "bad hex constant at line x in /etc/dnsmasq.conf" and this despite the fact that there is no error in mac addresses.

dhcp-host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

With only one of those two mac addresses, all is good, so there is no error in mac addresses. In the dnsmasq.conf they are other dhcp-host with multiple mac addresses like

dhcp-host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

and they are not rejected.

When copying the default configuration line in a dnsmasq-2.72-3 of Debian 8.7, no problem.

Description: Ubuntu 12.04.5 LTS
Release: 12.04

dnsmasq:
  Installé : 2.59-4ubuntu0.2
  Candidat : 2.59-4ubuntu0.2
 Table de version :
 *** 2.59-4ubuntu0.2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     2.59-4 0
        500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-116-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
Date: Wed Apr 12 15:25:20 2017
MarkForUpload: True
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

[Nish Aravamudan (nacc)]

Hello and thank you for filing this bug report. 12.04 has gone EOL in the meanwhile, though. Does this issue occur with Trusty or later?

[Dash (devel-tootai)]

As told in the original message, there was no problem with a dnsmasq-2.72-3 version of Debian 8. I downloaded the dnsmasq source version 2.76, compile it and problem is gone.

You can close this bug.