* Rune Kock wrote :
* Troy Piggins wrote:
My dnsmasq 2.41 doesn't seem to be assigning DHCP IP addresses.
Been running the server for some time, but mainly for the DNS
side of things. The IP addresses for most machines on my network
are static, so hasn't been a problem. But I'm trying to
On Tue, Nov 18, 2008 at 04:05, Troy Piggins t...@piggo.com wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
My dnsmasq 2.41 doesn't seem to be assigning DHCP IP addresses.
Been running the server for some time, but mainly for the DNS
side of things. The IP addresses for most machines on my
$ sudo iptables-save | grep 67
-A udpincoming_packets -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT
I'm not entirely fluent in iptables syntax, but to me this sounds like
accept packets with source port 67/68 AND dest port 67/68. I
believe that you need accept source port 67/68 OR
* Rune Kock wrote :
* Troy Piggins wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
My dnsmasq 2.41 doesn't seem to be assigning DHCP IP addresses.
Been running the server for some time, but mainly for the DNS
side of things. The IP addresses for most machines on my network
are static, so
Hello,
For some specific application I needed to deny access to a MAC address
to a lease. For this reason I modified the dhcp-script behavior and is
called with an extra parameter access once a dhcp request or discover
is received. In that case if the exit code of the script is zero,
dnsmasq
On Tue, Nov 18, 2008 at 07:09, Troy Piggins t...@piggo.com wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
My dnsmasq 2.41 doesn't seem to be assigning DHCP IP addresses.
Been running the server for some time, but mainly for the DNS
side of things.
* Rune Kock wrote :
On Tue, Nov 18, 2008 at 07:09, Troy Piggins t...@piggo.com wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
* Rune Kock wrote :
* Troy Piggins wrote:
snip /
$ sudo iptables-save | grep 67
-A udpincoming_packets -p udp -m udp --sport 67:68 --dport 67:68 -j ACCEPT
I'm a little more familiar with iptables, and Rune is right - there are
no rules in your INPUT table that accept the initial DHCP packets (which
don't have an IP address yet). Looks like eth0 is your external
interface, and eth1 is the internal one? then you want something like:
-A INPUT -i
