On Sun, 8 Dec 2019 11:27:56 +0100
Geert Stappers wrote:
> Time will tell how many OpenBSD users report here[1] "works for me"
works for me, both DHCP and DNS (OpenBSD 6.6, dnsmasq 2.80 from ports)
Note that you must not block UDP broadcasts or access to port 67 on the
interfaces that are served
Hi,
Alright, so I am an idiot. I should have done what you always do and
first test with a disabled firewall instead of banging my head against
the network config for three days. Things work fine with the firewall
out of the way.
The hint that got me there came from the dnsmasq FAQ. It mentions t
On Sun, Dec 08, 2019 at 01:29:45AM +0200, Fabian wrote:
>
> I was playing around a bit more with fstat and netstat and noticed one
> difference between dhcpd and dnsmasq - dhcpd binds to bpf (Berkeley
> Packet Filter) and not a datagram socket like dnsmasq does. I
> definitely see a UDP datagram c
On Sat, 7 Dec 2019 21:44:08 +0100
Geert Stappers wrote:
> A. stop dnsmasq and check again what fstat says about port 67
Nothing else is listening on that port.
> B. try only 1 interface (add the others I/F when 1 works)
Could not make that work. :-(
> > inet 182.227.21.34 netmask 0xf
On Sat, Dec 07, 2019 at 09:38:07PM +0200, dnsm...@mailfri.com wrote:
> Hi,
>
> I am trying to run the dnsmasq 2.80 port on my OpenBSD home router and
> am failing miserably at soliciting any response for DHCP requests. I am
> reasonably sure that my firewall and routing settings are good because
>
Hi,
I am trying to run the dnsmasq 2.80 port on my OpenBSD home router and am
failing miserably at soliciting any response for DHCP requests. I am reasonably
sure that my firewall and routing settings are good because the dhcpd that
comes with OpenBSD works just fine (and I can see DHCP request
