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

Thread: AP300 Issues

  1. #1
    Junior Member
    Join Date
    Feb 2017
    Posts
    1

    AP300 Issues

    Model : AP300

    Hardware Version :

    Firmware Version : 1.0.0 Build 20160114 Rel. 34427

    ISP : [/COLOR]

    Hi,

    I have an AP300 configured as an access point with 1 2.4G and 1 5G SSID. Currently using WPA2 Enterprise.

    First issue is my DHCP server is being flooded with IP address renewals. Every 30s the AP requests a new IP. Setting a static IP does not stop the issue. DHCP Server on the AP is disabled.

    Second issue is throughput. Downloads start at full speed then soon tail off and stop. Web browsing is also affected. AP is connected to a 1Gbps Cisco Switch and running at 1000Mb/Full. No issues with the wired network.

    I've tried WPA2 Personal but this does not help. Factory reset not fixed either.

    Any ideas? No hope of applying a new firmware as there isn't one available.

    Help Please!

    Thanks.

  2. #2
    Junior Member
    Join Date
    Feb 2017
    Posts
    1
    I have the exact same issue with the DHCP refresh, which was reported by a user on Amazon.co.uk (Link), but I didn't think it would be a big issue, as nothing in my house uses DHCP. As it stands though, this is causing trouble with other devices. I have always had this device in Static IP Client mode, and 7 devices connect to it over Ethernet, all of which are configured to use static IP addresses.
    Infact the only device in my house that requires DHCP is my Chromecast, which for some reason does not allow Static IP addressing.
    Anyway, this issue persists even when I disable my DHCP service:


    ################################################## #########################
    # AP300 System Log
    # H-Ver = AP300 v1.0 : S-Ver = 1.0.0 Build 20160114 Rel. 34427
    ################################################## #########################


    1st day 13:00:08 OTHER INFO All system logs were cleared.
    1st day 13:00:10 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:00:14 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:00:16 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:00:18 DHCP NOTICE DHCPC DHCP Service unavailable, recv no OFFER
    1st day 13:00:36 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 13:00:36 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:00:38 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:00:40 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:00:44 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:00:46 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:00:48 DHCP NOTICE DHCPC DHCP Service unavailable, recv no OFFER
    1st day 13:01:07 DHCP NOTICE DHCPC perform a DHCP renew
    1st day 13:01:07 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:01:09 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:01:11 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 0
    1st day 13:01:15 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:01:17 DHCP NOTICE DHCPC Send DISCOVER with request ip 192.168.10.3 and unicast flag 1
    1st day 13:01:19 DHCP NOTICE DHCPC DHCP Service unavailable, recv no OFFER

    I have also noticed the serious problem which is that it seems to be routing traffic to itself when the traffic should be a DNS request. All of my devices use 192.168.0.5 (for internal and a mirror of google's DNS) and 8.8.8.8 (Google's DNS), but for some reason, sometimes traffic intended for 0.5 gets sent to 0.1 (The Wireless AP) with the destination address of 0.3 (This device, the AP300). I havent investigated this issue for long, so it may do this with other traffic too. It does mean that for about 30 seconds out of every 15 minutes or so, DNS requests go unresolved. I have not noticed any bandwidth slowdowns, however.

    One final problem that I can't seem to diagnose is that sometimes devices that are connected to the AP300 are just not able to connect beyond that, the receive connection failure responses from the AP300, and this is while other devices which are connected to the AP300 are working correctly without issue. The only solution I have found for this is to use a working device to reboot the AP300.

    I think I'm just going to send this back, its causing more headaches than I would like.

  3. #3
    Model : AP300
    Hardware Version :
    Firmware Version : 1.0.0 Build 20160114 Rel. 34427

    Hi, here also the exact same DHCP behavior issue.
    I just bought the AP, and 2h later already want to send it back.
    I'm even more disapointed seeing that almost all posts have absolutely no views, and no formal answers from TP-Link staff.
    1st TP-link product, last one ?

  4. #4

  5. #5
    Hi, yes i have received this beta firmware from TP-link support.
    I confirm it stops the DHCP request flood.
    Still the AP raise a DHCP lease request when booting.
    But hey, it's an improvment right ?

    Happy to pay a product to be beta tester, is that some kind of "early access" game that will never be finished ?


 

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.