[Dnsmasq-discuss] Logging of DHCP activity [Re: Dnsmasq-discuss Digest, Vol 72, Issue 21]

Modem Man modem-man at gmx.net
Wed May 25 20:42:13 BST 2011


> Today's Topics:
>
>    1. Logging of DHCP activity (dnsmasq at lovelady.com)
>
> [...]
> lovestora-1 /home/delovelady> tail -20 /home/messages
> [...]
>
> May 24 05:08:21 lovestora-1 dnsmasq-dhcp[2037]: DHCPDISCOVER(eth0)
> 192.168.0.10 00:1d:09:59:7b:7c
>
> May 24 05:08:21 lovestora-1 dnsmasq-dhcp[2037]: DHCPOFFER(eth0) 192.168.0.10
> 00:1d:09:59:7b:7c
>
> May 24 05:08:21 lovestora-1 dnsmasq-dhcp[2037]: DHCPREQUEST(eth0)
> 192.168.0.10 00:1d:09:59:7b:7c
>
> May 24 05:08:21 lovestora-1 dnsmasq-dhcp[2037]: DHCPACK(eth0) 192.168.0.10
> 00:1d:09:59:7b:7c m1330c
> [...]
>
> and so on
>   
1st, I can not detect both interfaces trying to fight about the one and
only IP address, as you guessed in the answer posting.
Your logs all times report only Dell Eth0 (00:1d:09:59:7b:7c), but never
the Intel wlan0 (00:21:5c:6a:03:ef).
Did I missed somewhat? Or are you still on the wrong track?

My 1st guess has been: Windoze has accidentially firewalled parts of the
DHCP...
But this might also be wrong, because I think the DHCPOFFER must have
been seen by windows. Who knows...

> domain=lovelady.com
>
> dhcp-range=192.168.0.10,192.168.0.109,7d
>   
I think your domain is not a good idea. It doesn't cause the seen
problems to you. And it might not cause any problems to you, if you own
this domain.
But if you are connected to the internet, you should better not use
official domains for private local networks, like you 192.168/16 is.
A not routed / test domain like lovelady.home should be advised, IIRC.

This all may not help you to fix the problem, but you should think about
the one or other issue.
And if I'm wrong, you could teach me the right answers, so I can improve
_my_ setup ;-)

Greetings,
Modem Man




More information about the Dnsmasq-discuss mailing list