See release notes on Dnsmasq 2.35
http://freshmeat.net/projects/dnsmasq/?branch_id=1991&release_id=239661
"OpenBSD-4.0 is due for release very soon and no version of dnsmasq
prior to 2.35 will do DHCP on OpenBSD-4.0."
/Markus
Manuel Ravasio wrote:
Hello all.
I'm trying to set up a firewall/web-proxy/dns-proxy/dhcp-server box at
home, using a quite old i386-based pc (AMD k6-2 300, 256mb RAM, 2x10G
IDE disks) and OpenBSD 4.0.
OS installation, disk management, additional software installation and
configuration... everything went fine.
Problems started in configuring dnsmasq: I managed to make dns
forwarding work ( I really don't need anything more than standard
behaviour), then I created a DHCP range entry:
expand-hosts
domain=manuel.test
dhcp-range=192.168.2.100,192.168.2.200,255.255.255.0,1h
I chose to activate dnsmasq on the "internal" intercace only:
interface=pcn1
pcn1,'s IP address is fixed and compatible with the range specified:
# ifconfig pcn1
pcn1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:0c:29:af:4f:47
media: Ethernet autoselect (autoselect)
inet 192.168.2.11 netmask 0xffffff00 broadcast 192.168.2.255
inet6 fe80::20c:29ff:feaf:4f47%pcn1 prefixlen 64 scopeid 0x2
I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes
dnsmasq start the dhcp service automatically, but alas DHCP server
apparently doesn't work: linux and windows clients can't grab IP
addresses and other IP information, and netstat doesn't show anything
listening on port 67/68.
# ps -aux | grep dns
nobody 16166 0.0 0.3 520 648 ?? S 12:58PM 0:00.00 dnsmasq
# netstat -an | grep tcp | grep -v tcp6
tcp 0 0 127.0.0.1.53 *.* LISTEN
tcp 0 0 192.168.2.11.53 *.* LISTEN
tcp 0 0 127.0.0.1.6010 *.* LISTEN
tcp 0 0 192.168.2.11.22 192.168.2.1.48605
ESTABLISHED
tcp 0 0 *.22 *.* LISTEN
What am I missing?
Thank you everybody for your kind help.
Byee,
Manuel