Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 5 of 5
  1. #1

    AP500 DHCP requests when on static

    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    I have a AP500 set with a static IP and the DHCP on it turned off as my Draytek Modem handles DHCP.
    I did a network scan and saw the AP500 appearing twice in the list, once on its static IP and again on an IP in the DHCP range, so I checked the system logs on the AP500 is requesting an IP.

    1st day 00:20:47 DHCP NOTICE DHCPC Entering released state
    1st day 00:21:16 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 00:21:16 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.1.6 and unicast flag 0
    1st day 00:21:16 DHCP NOTICE DHCPC Recv OFFER from server 192.168.1.254 with ip 192.168.1.6
    1st day 00:21:16 DHCP NOTICE DHCPC Send REQUEST to server 192.168.1.254 with request ip 192.168.1.6
    1st day 00:21:17 DHCP NOTICE DHCPC Recv ACK from server 192.168.1.254 with ip 192.168.1.6 lease time 172800
    1st day 00:21:17 DHCP NOTICE DHCPC:GET ip:192.168.1.6 mask:255.255.255.0 gateway:192.168.1.254 dns1:192.168.1.254 dns2:8.8.8.8 static route:0
    1st day 00:21:18 DHCP NOTICE DHCPC Unicasting a release of 192.168.1.6 to 192.168.1.254
    1st day 00:21:18 DHCP NOTICE DHCPC Entering released state
    1st day 00:21:46 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 00:21:46 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.1.6 and unicast flag 0
    1st day 00:21:46 DHCP NOTICE DHCPC Recv OFFER from server 192.168.1.254 with ip 192.168.1.6
    1st day 00:21:46 DHCP NOTICE DHCPC Send REQUEST to server 192.168.1.254 with request ip 192.168.1.6
    1st day 00:21:48 DHCP NOTICE DHCPC Recv ACK from server 192.168.1.254 with ip 192.168.1.6 lease time 172800
    1st day 00:21:48 DHCP NOTICE DHCPC:GET ip:192.168.1.6 mask:255.255.255.0 gateway:192.168.1.254 dns1:192.168.1.254 dns2:8.8.8.8 static route:0
    1st day 00:21:49 DHCP NOTICE DHCPC Unicasting a release of 192.168.1.6 to 192.168.1.254
    1st day 00:21:49 DHCP NOTICE DHCPC Entering released state
    1st day 00:22:17 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 00:22:17 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.1.6 and unicast flag 0
    1st day 00:22:17 DHCP NOTICE DHCPC Recv OFFER from server 192.168.1.254 with ip 192.168.1.6
    1st day 00:22:17 DHCP NOTICE DHCPC Send REQUEST to server 192.168.1.254 with request ip 192.168.1.6
    1st day 00:22:18 DHCP NOTICE DHCPC Recv ACK from server 192.168.1.254 with ip 192.168.1.6 lease time 172800
    1st day 00:22:18 DHCP NOTICE DHCPC:GET ip:192.168.1.6 mask:255.255.255.0 gateway:192.168.1.254 dns1:192.168.1.254 dns2:8.8.8.8 static route:0
    1st day 00:22:19 DHCP NOTICE DHCPC Unicasting a release of 192.168.1.6 to 192.168.1.254
    1st day 00:22:19 DHCP NOTICE DHCPC Entering released state
    1st day 00:22:47 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 00:22:47 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.1.6 and unicast flag 0
    1st day 00:22:47 DHCP NOTICE DHCPC Recv OFFER from server 192.168.1.254 with ip 192.168.1.6
    1st day 00:22:47 DHCP NOTICE DHCPC Send REQUEST to server 192.168.1.254 with request ip 192.168.1.6
    1st day 00:22:48 DHCP NOTICE DHCPC Recv ACK from server 192.168.1.254 with ip 192.168.1.6 lease time 172800
    1st day 00:22:48 DHCP NOTICE DHCPC:GET ip:192.168.1.6 mask:255.255.255.0 gateway:192.168.1.254 dns1:192.168.1.254 dns2:8.8.8.8 static route:0
    1st day 00:22:49 DHCP NOTICE DHCPC Unicasting a release of 192.168.1.6 to 192.168.1.254
    1st day 00:22:49 DHCP NOTICE DHCPC Entering released state

    Why would it be doing this when its set to use a static?

  2. #2
    I got a reply from the TP-LINK support, this is a bug , they said they will release a beta firmware to fix it.

  3. #3
    Quote Originally Posted by little Anthony View Post
    I got a reply from the TP-LINK support, this is a bug , they said they will release a beta firmware to fix it.
    Cheers, just got the same response from them. For now i have just set up a DHCP lease using the IP address I want the device to have.

  4. #4
    I saw this too, we are on 2017, is this device abandoned by tp-link?

  5. #5
    The official firmware on the website has not changed since 24/11/15 and my beta firmware fixing multi ssid is from 07/06/16.
    Its a shame ... But who cares @ tp-link - Lesson learned - Other vendor next time.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.