[9.060][MYTH] DHCP gives wrong IP?

Hi there,

it seems that the DHCP Server is ginving sometimes ip 10.10.122.100 instead of the configured 10.10.122.15

i see the following in the logs:

dhcpd-2013-01-26.log:2013:01:26-09:04:45 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.100 (10.10.122.1) from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
dhcpd-2013-01-26.log:2013:01:26-09:04:45 firewall-1 dhcpd: DHCPACK on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
dhcpd-2013-01-26.log:2013:01:26-19:52:05 firewall-1 dhcpd: DHCPOFFER on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
dhcpd-2013-01-26.log:2013:01:26-19:52:05 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 (10.10.122.1) from 00:1a:8c:0c:e2:36 via eth1.122

in the DHCP-config-files i found:

dhcpd.leases:

lease 10.10.122.100 {
  starts 6 2013/01/26 08:04:45;
  ends 6 2013/01/26 18:44:16;
  tstp 6 2013/01/26 18:44:16;
  cltt 6 2013/01/26 08:04:45;
  binding state free;
  hardware ethernet 00:1a:8c:0c:e2:36;
  uid "\001\000\032\214\014\3426";
}

dhcpd.conf:

    host REF_NetHosGaestezimm {
      hardware ethernet 00:1a:8c:0c:e2:36;
      fixed-address 10.10.122.15;
    }

and a bit more out of the dhcpd.logs:

2013:01:26-09:03:07 firewall-1 dhcpd: DHCPACK on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.100 (10.10.122.1) from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPACK on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:03:14 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:04:44 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:04:45 firewall-1 dhcpd: DHCPOFFER on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:04:45 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.100 (10.10.122.1) from 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-09:04:45 firewall-1 dhcpd: DHCPACK on 10.10.122.100 to 00:1a:8c:0c:e2:36 (AP50-A4000207AA91A9C) via eth1.122
2013:01:26-19:52:05 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:26-19:52:05 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:26-19:52:05 firewall-1 dhcpd: DHCPOFFER on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:26-19:52:05 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:26-19:52:05 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 (10.10.122.1) from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:26-19:52:05 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-07:52:06 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:27-07:52:06 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-07:52:06 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-15:06:57 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:27-15:06:57 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-15:06:57 firewall-1 dhcpd: DHCPOFFER on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-15:06:57 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:27-15:06:57 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 (10.10.122.1) from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:27-15:06:57 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-03:06:57 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-03:06:57 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-03:06:57 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-15:06:58 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-15:06:58 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-15:06:58 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-17:22:53 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-17:22:53 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-17:22:53 firewall-1 dhcpd: DHCPOFFER on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-17:22:53 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-17:22:53 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 (10.10.122.1) from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-17:22:53 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-18:42:23 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-18:42:23 firewall-1 dhcpd: DHCPDISCOVER from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-18:42:23 firewall-1 dhcpd: DHCPOFFER on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-18:42:23 firewall-1 dhcpd: uid lease 10.10.122.100 for client 00:1a:8c:0c:e2:36 is duplicate on 10.10.122.0/24
2013:01:28-18:42:23 firewall-1 dhcpd: DHCPREQUEST for 10.10.122.15 (10.10.122.1) from 00:1a:8c:0c:e2:36 via eth1.122
2013:01:28-18:42:23 firewall-1 dhcpd: DHCPACK on 10.10.122.15 to 00:1a:8c:0c:e2:36 via eth1.122
firewall:/var/log/dhcpd/2013/01 #

Thanks
Robert

0 Tinkerbell over 12 years ago

Hey Robert

We will try to reproduce this issue with an AP50 in our setup. Will keep u posted.
Cheers!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 utm_kid over 12 years ago in reply to Tinkerbell

ok ,quick quastion

is AP 10 support ip v6 by default ?
does AP 50 support ipv6 by default (support both 4 and 6 ) ?

if AP 10 doesnt support ipv6 and AP 50 support ipv6 then i "think " this the same problem i had https://community.sophos.com/products/unified-threat-management/astaroorg/f/80/t/64794

thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 da_merlin over 12 years ago

Please wait a week and see if the client still gets the non-static lease.
Client probably requests the old IP address and DHCP serves still the old
IP because a valid lease is found. Valid lease should get invalid after one week.

Cheers
Ulrich
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Robert Tausend over 12 years ago

Hi Ulrlich,

shoudn't the lease be deletet when we create a new static mapping?

Robert
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 da_merlin over 12 years ago

Maybe in a perfect world yes [;)] But it was that way since ASL v4.0 and nobody complained loud enough so far...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tinkerbell over 12 years ago in reply to Robert Tausend

shoudn't the lease be deletet when we create a new static mapping?

For the static mapping to be in use you have to manually release/renew the IP on the DHCP client.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Robert Tausend over 12 years ago

what i can't on a AP50 Bianca, maybe Helmut can adapt it? haha [[[:)]]]

but you are right Ulrich [[[:)]]] no one complained loud enough [[[:)]]]

thanks

robert
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tinkerbell over 12 years ago in reply to Robert Tausend

Hi Robert,

what i can't on a AP50 Bianca, maybe Helmut can adapt it? haha [[:)]]

The static mapping will take over after you delete the AP from Wireless Protection->AP->Active AP. That's what i ment by "release/renew". [[:)]] Or you can always try the good old classy way: hw reset.
The DHCP process will not start again unless you trigger it. Either by what i mentioned above, or just by waiting for the lease time to be over. Also, you could change the lease time in the DHCP Server option and set it to a lower time (600 seconds is the lowest possible).
Cheers,
Bianca
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel