Should I see port 67 listening when dnsmasq is running? I ran nmap with this result:
Starting Nmap 4.11 ( http://www.insecure.org/nmap/
) at 2007-06-03 08:50 PDT
Interesting ports on fileserv.yerke.local (127.0.0.1):
Not shown: 1666 closed ports
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 4.4 (protocol 1.99)
25/tcp open smtp Sendmail 8.13.8/8.13.8
37/tcp open time (32 bits)
53/tcp open domain ISC Bind dnsmasq-2.33
80/tcp open http Apache httpd 2.2.4 ((Unix) mod_ssl/2.2.4 OpenSSL/0.9.8d DAV/2 PHP/5.2.2)
111/tcp open rpcbind 2 (rpc #100000)
113/tcp open ident OpenBSD identd
139/tcp open netbios-ssn Samba smbd 3.X (workgroup: MSHOME)
445/tcp open netbios-ssn Samba smbd 3.X (workgroup: MSHOME)
587/tcp open smtp Sendmail 8.13.8/8.13.8
631/tcp open ipp CUPS 1.1
752/tcp open status 1 (rpc #100024)
5432/tcp open postgresql PostgreSQL DB
6881/tcp open tcpwrapped
Service Info: OSs: Unix, OpenBSD
as you can see, dnsmasq is listening on 53 for DNS requests, but not on 67 for DHCP. I have uncommented and edited the dhcp-range option in the config file. If I try to use dhcp to assign addresses, there is no reply. Wireshark indicates that requests are getting into the machine through the firewall.
I am using Slackware 11.0 with dnsmasq 3.5 package from LinuxPackages.
I tuned off bind so that dnsmasq would have port 53 open to start.
I hope this is enough info.