<HTML>
<P>thanks for the quick response <BR>
<BR>
i tried installing 2.39 from source as there is not a openbsd pkg for it <BR>
<BR>
and get <BR>
####<BR>
[/home/user/dnsmasq-2.39]<BR>
->sudo make install<BR>
make I18N=-DNO_GETTEXT -f ../bld/Makefile -C src dnsmasq<BR>
make: unknown option -- C<BR>
usage: make [-BeiknPqrSst] [-D variable] [-d flags] [-f makefile]<BR>
[-I directory] [-j max_jobs] [-m directory] [-V variable]<BR>
[NAME=value] [target ...]<BR>
*** Error code 2</P>
<P>Stop in /home/user/dnsmasq-2.39 (line 15 of Makefile).<BR>
####<BR>
<BR>
is it a problem to install using sudo?<BR>
<BR>
do i need to be a in a different directory?<BR>
<BR>
<BR>
<BR>
<B>On Tue May 8 23:17 , Simon Kelley <SIMON@THEKELLEYS.ORG.UK>sent:<BR>
<BR>
</P></B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #f5f5f5 2px solid; MARGIN-RIGHT: 0px">Wesley Connor wrote:<BR>
> howdy folks<BR>
> <BR>
> i have what i believe is a common problem, but im damned if i can figure<BR>
> out how to fix it<BR>
> <BR>
> i have a 2 day old install of openbsd 4.1 running the latest pkg version<BR>
> of dnsmasq which is 2.31<BR>
> <BR>
> i have dnsmasq setup doing dns and dhcp on my server and the dns is<BR>
> working fine<BR>
> <BR>
> but when clients request a dhcp lease, on the server i get<BR>
> <BR>
> dnsmasq[30314]: DHCPDISCOVER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> dnsmasq[30314]: DHCPOFFER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> dnsmasq[30314]: DHCPDISCOVER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> dnsmasq[30314]: DHCPOFFER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> dnsmasq[30314]: DHCPDISCOVER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> dnsmasq[30314]: DHCPOFFER(fxp0) 192.168.101.15 00:0c:6e:66:##:##<BR>
> <BR>
> repeated about a dozen times<BR>
> <BR>
> but no DHCPDACK's and the client eventually times out<BR>
> <BR>
> now as i understand this is a broadcast/firewall filtering issue<BR>
> <BR>
> my pf is setup to allow all in and all out and ive tried it with pf<BR>
> disabled<BR>
> <BR>
> the if im listening on is setup as<BR>
> <BR>
> inet 192.168.101.100 255.255.255.0 NONE<BR>
> <BR>
> which gives it an ifconfig response of<BR>
> <BR>
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500<BR>
> lladdr 00:90:27:2e:##:##<BR>
> groups: egress<BR>
> media: Ethernet autoselect (100baseTX full-duplex)<BR>
> status: active<BR>
> inet6 fe80::290:27ff:fe2e:7fd6%fxp0 prefixlen 64 scopeid 0x1<BR>
> inet 192.168.101.100 netmask 0xffffff00 broadcast 192.168.101.255<BR>
> <BR>
> <BR>
> my dnsmasq.conf contains<BR>
> ####<BR>
> domain-needed<BR>
> bogus-priv<BR>
> <BR>
> filterwin2k<BR>
> <BR>
> interface=fxp0<BR>
> <BR>
> expand-hosts<BR>
> <BR>
> domain=foo.org<BR>
> <BR>
> dhcp-range=192.168.101.2,192.168.101.200,12h<BR>
> <BR>
> dhcp-option=3,192.168.101.1 #mygateway<BR>
> <BR>
> dhcp-authoritative<BR>
> <BR>
> log-queries<BR>
> ###<BR>
> <BR>
> am i missing something obvious?<BR>
<BR>
No, your config looks fine.<BR>
> <BR>
> as i said the dns is working fine<BR>
> <BR>
> and the dhcp requests seem to be getting in and dnsmasq is offering an ip<BR>
> the leases just arent 'getting out' or being picked up<BR>
> <BR>
> and as in the other cases i have read, the standard dhcpd works fine but<BR>
> i understand that it works differently<BR>
<BR>
That's probably no relevant: under Linux dnsmasq does DHCP differently<BR>
to dhcpd, but on *BSD, pretty much the same constraints apply, I think.<BR>
<BR>
There's a history of bugs on OpenBSD 4.x which might be relevant: 2.31<BR>
will not work at all under OpenBSD 4.0 because of a kernel bug: a<BR>
work-around went into versions 2.35 and up, but that should only be<BR>
active under 4.0. The kernel bug was fixed in a test kernel I have,<BR>
which was supposed to go into 4.1, but I've not verified that it did.<BR>
The symptoms of that bug were different to what you see (no logging at<BR>
all, all DHCP packets ignored.)<BR>
<BR>
Please could you try the latest release of dnsmasq, (2.39) and if that<BR>
doesn't work, try and grab the packets using tcpdump, and trace the<BR>
execution of the program using truss. Mail me the complete raw packet<BR>
dump file. (Mail me off list if you need more explicit instructions on<BR>
doing that.)<BR>
<BR>
<BR>
Cheers,<BR>
<BR>
Simon.<BR>
<BR>
<BR>
</BLOCKQUOTE></HTML>
<BR>