Re: [Dnsmasq-discuss] DNSMasq, DHCP, Shorewall, and Proxy Arp

2008-02-02 Thread Steve H.
Gaah - re-adding the mailing list.. On Saturday 02 February 2008 03:22:01 pm you wrote: > On Feb 2, 2008 3:48 PM, Steve H. wrote: > > On Saturday 02 February 2008 01:03:06 pm you wrote: > > > This won't work, because 1.2.3.4 is outside the local subnet of the > > > device, which therefore uses a

[Dnsmasq-discuss] "possible DNS-rebind attack detected" ??

2008-02-02 Thread Carlos Carvalho
I use --stop-dns-rebind and I'm getting "possible DNS-rebind attack detected" msgs. in the log. This happens after a series of nxdomain answers (from the recursor or cached). I don't understand why this is a possible attack because the manual says that this should be triggered by answers within pri

Re: [Dnsmasq-discuss] DNSMasq, DHCP, Shorewall, and Proxy Arp

2008-02-02 Thread richardvo...@gmail.com
On Feb 2, 2008 4:56 AM, Steve H. wrote: > > Hello, > > I've been trying to figure out how to get DNSMasq setup to serve DHCP for my > networks. I have a firewall setup according to the Shorewall > (http://www.shorewall.net ) proxy arp configuration. My firewall has two > interfaces : > eth0

Re: [Dnsmasq-discuss] dnsmasq 2.41 release candidate.

2008-02-02 Thread Simon Kelley
Matthias Andree wrote: Simon Kelley writes: Changelog from 2.40: Remove deprecated calls when compiled against libdbus 1.1. Fix "strict-alias" warning in bpf.c Reduce dependency on Gnu-make in build system: dnsmasq now builds with system make und

Re: [Dnsmasq-discuss] dnsmasq 2.41 release candidate.

2008-02-02 Thread Matthias Andree
Simon Kelley writes: > Changelog from 2.40: > > Remove deprecated calls when compiled against libdbus 1.1. > > Fix "strict-alias" warning in bpf.c > > Reduce dependency on Gnu-make in build system: dnsmasq now > builds with system make under OpenBSD

[Dnsmasq-discuss] DNSMasq, DHCP, Shorewall, and Proxy Arp

2008-02-02 Thread Steve H.
Hello,   I've been trying to figure out how to get DNSMasq setup to serve DHCP for my networks.  I have a firewall setup according to the Shorewall (http://www.shorewall.net ) proxy arp configuration.  My firewall has two interfaces :   eth0 1.2.3.4 (routable, internet facing)   eth1 192.168.0