[Dnsmasq-discuss] DNSMasq and Windows 7

[Didster]

Brielle, thanks very much

Adding dhcp-option=252,\n\000

Has fixed it - Windows 7 is now accepting the IP.  Flamin' M$!

Perhaps Simon could add this to the FAQ?

Thanks again


> I had this odd behavior at one point - are you able to run a
> tcpdump/tshark of the LAN interface on the machine hosting DNSmasq?  If so,
> have it monitor port 67/68:
>
> tshark -i eth1 port 67 or port 68
>
>
> I have two ideas - first, you may have an iptables rule affecting this.
>  These are the iptables rules I use to make sure DHCP works correctly:
>
> iptables -I INPUT -i eth1 -p udp --dport 67:68 --sport 67:68 -j ACCEPT
>
>
>
> the second could be remotely related to what I talk about here:
>
> http://brielle.sosdg.org/**archives/522-Windows-7-**
> flooding-DHCP-server-with-**DHCPINFORM-messages.html<http://brielle.sosdg.org/archives/522-Windows-7-flooding-DHCP-server-with-DHCPINFORM-messages.html>
>
>
>
>
>
>
>
> --
> Brielle Bruns
> The Summit Open Source Development Group
> http://www.sosdg.org    /     http://www.ahbl.org
>
>
>
>
> ---------- Forwarded message ----------
> From: Brielle Bruns <bruns at 2mbit.com>
> To: dnsmasq-discuss at lists.thekelleys.org.uk
> Cc:
> Date: Wed, 28 Dec 2011 16:19:25 -0700
> Subject: Re: [Dnsmasq-discuss] DNSMasq and Windows 7
> oops, meant to send this to the list!
>
> On 12/28/11 3:52 PM, Didster wrote:
>
>> Hello,
>>
>> I have been running DNSMasq for some time now on a network consisting
>> mainly of Windows XP and Linux machines, with no problems at all.
>>
>> I brought my daughter a new laptop for Christmas and it came with
>> Windows 7.  Sadly, this is what she uses at school so I have to stick
>> with it.
>>
>> For some reason, it refuses to accept IP addresses handed out by
>> DNSMasq.  Logs are full of:
>>
>> Dec 28 21:29:21 gateway dnsmasq-dhcp[27812]: DHCPREQUEST(eth0)
>> 192.168.0.190 ac:72:89:11:44:32
>> Dec 28 21:29:21 gateway dnsmasq-dhcp[27812]: DHCPACK(eth0) 192.168.0.190
>> ac:72:89:11:44:32 millsy-PC
>> Dec 28 21:29:26 gateway dnsmasq-dhcp[27812]: DHCPREQUEST(eth0)
>> 192.168.0.190 ac:72:89:11:44:32
>> Dec 28 21:29:26 gateway dnsmasq-dhcp[27812]: DHCPACK(eth0) 192.168.0.190
>> ac:72:89:11:44:32 millsy-PC
>> Dec 28 21:29:40 gateway dnsmasq-dhcp[27812]: DHCPREQUEST(eth0)
>> 192.168.0.190 ac:72:89:11:44:32
>> Dec 28 21:29:40 gateway dnsmasq-dhcp[27812]: DHCPACK(eth0) 192.168.0.190
>> ac:72:89:11:44:32 millsy-PC
>> Dec 28 21:29:50 gateway dnsmasq-dhcp[27812]: DHCPREQUEST(eth0)
>> 192.168.0.190 ac:72:89:11:44:32
>> Dec 28 21:29:50 gateway dnsmasq-dhcp[27812]: DHCPACK(eth0) 192.168.0.190
>> ac:72:89:11:44:32 millsy-PC
>>
>> Over and over.  But Windows 7 just refuses to accept the IP.  Turing off
>> DNSMasq and enabling the DHCP server on my router works just fine on the
>> W7 machine.
>>
>> I am running the version of DNSMasq currently in Debian Sid - 2.59.
>>
>>
>
> I had this odd behavior at one point - are you able to run a
> tcpdump/tshark of the LAN interface on the machine hosting DNSmasq?  If so,
> have it monitor port 67/68:
>
> tshark -i eth1 port 67 or port 68
>
>
> I have two ideas - first, you may have an iptables rule affecting this.
>  These are the iptables rules I use to make sure DHCP works correctly:
>
> iptables -I INPUT -i eth1 -p udp --dport 67:68 --sport 67:68 -j ACCEPT
>
>
>
> the second could be remotely related to what I talk about here:
>
> http://brielle.sosdg.org/**archives/522-Windows-7-**
> flooding-DHCP-server-with-**DHCPINFORM-messages.html<http://brielle.sosdg.org/archives/522-Windows-7-flooding-DHCP-server-with-DHCPINFORM-messages.html>
>
>
> --
> Brielle Bruns
> The Summit Open Source Development Group
> http://www.sosdg.org    /     http://www.ahbl.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20111229/01299320/attachment.html>