1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Dnsmasq DHCP -- Excessive lease negotiation

Discussion in 'Tomato Firmware' started by Planiwa, Feb 19, 2009.

  1. Planiwa

    Planiwa LI Guru Member

    With 7-day "static" leases, why do some devices insist on renegotiating a new lease every few minutes? Look:

    From Device List:

    Code:
    192.168.0.114	ando-i	-79 dBm	12 	6 days, 23:52:33
    From /var/log/messages:

    Code:
    Feb 19 15:28:40 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPDISCOVER(br0) 00:21:an:ip:ho:ne
    Feb 19 15:28:41 ROUTER daemon.info dnsmasq[122]: DHCPOFFER(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:42 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:28:42 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPDISCOVER(br0) 00:21:an:ip:ho:ne
    Feb 19 15:34:12 ROUTER daemon.info dnsmasq[122]: DHCPOFFER(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:13 ROUTER daemon.info dnsmasq[122]: DHCPREQUEST(br0) 192.168.0.114 00:21:an:ip:ho:ne
    Feb 19 15:34:13 ROUTER daemon.info dnsmasq[122]: DHCPACK(br0) 192.168.0.114 00:21:an:ip:ho:ne ando-i
    
    Anyone know what's going on here?

    [Addendum -- from another site -- this is a laptop, AFAIK]:

    Code:
    Feb 19 17:06:19 ROUTER daemon.info dnsmasq[20782]: DHCPREQUEST(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:06:19 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name
    Feb 19 17:06:35 ROUTER daemon.info dnsmasq[20782]: DHCPINFORM(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:06:35 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name-host
    Feb 19 17:06:37 ROUTER daemon.info dnsmasq[20782]: DHCPINFORM(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:06:37 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name-host
    Feb 19 17:08:17 ROUTER daemon.info dnsmasq[20782]: DHCPDISCOVER(br0) 00:14:nn:aa:mm:ee
    Feb 19 17:08:17 ROUTER daemon.info dnsmasq[20782]: DHCPOFFER(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:08:17 ROUTER daemon.info dnsmasq[20782]: DHCPREQUEST(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:08:17 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name
    Feb 19 17:08:22 ROUTER daemon.info dnsmasq[20782]: DHCPINFORM(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:08:22 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name-host
    Feb 19 17:08:30 ROUTER daemon.info dnsmasq[20782]: DHCPINFORM(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:08:30 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name-host
    Feb 19 17:08:33 ROUTER daemon.info dnsmasq[20782]: DHCPINFORM(br0) 192.168.0.122 00:14:nn:aa:mm:ee
    Feb 19 17:08:33 ROUTER daemon.info dnsmasq[20782]: DHCPACK(br0) 192.168.0.122 00:14:nn:aa:mm:ee name-host
    
     
  2. fyellin

    fyellin LI Guru Member

    We've got two iphones in our household, and the logs are filled with this.

    I suspect that everytime the iphone wakes up, it needs to verify that it's still where it things it is and that its old IP address is still good. Laptops seem content with "Hmm, I'm still talking to the same base station, and my lease is still good."

    In any case, I suspect that there's either something very clever or something very broken in the iPhone. Don't worry about it.
     
  3. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    My Wii does the same thing. I don't think it's a problem (well, by that I mean nothing is wrong with your setup - the iPhone/Wii behavior on the other hand....).
     
  4. mstombs

    mstombs Network Guru Member

    It is not dnsmasq's problem it is the client - Windows XP also does this when it thinks it has lost contact with the gateway - its an active way of waking up some devices I guess.
     

Share This Page