Home Network Community > Range Extenders > Connectivity issue with TP-Link AX1500 in Access Point mode
< Range Extenders

Connectivity issue with TP-Link AX1500 in Access Point mode

Connectivity issue with TP-Link AX1500 in Access Point mode

Connectivity issue with TP-Link AX1500 in Access Point mode
Connectivity issue with TP-Link AX1500 in Access Point mode
2025-09-25 15:22:48 - last edited 2025-10-16 11:35:30
Model: RE505X  
Hardware Version: V2
Firmware Version: 1.1.0 Build 20241224 Rel. 35085

I am using a TP-Link AX1500 device in Access Point (AP) mode, connected via LAN cable to my main router (IP: 192.168.1.1, DHCP enabled).

  • In AP mode with LAN connection, devices that connect to the TP-Link Wi-Fi get disconnected after some time.

  • In extender mode (without LAN), Wi-Fi works fine without disconnections.

  • It seems to be related to a possible IP/DHCP conflict when the LAN cable is connected.

Request:
Please investigate this issue and provide a fix or recommended configuration for stable connectivity in AP mode with LAN backhaul.

Device details:

  • Model: TP-Link AX1500 (https://www.amazon.in/dp/B0859M6P2C?ref=ppx_yo2ov_dt_b_fed_asin_title)

  • Hardware Version: RE505X v2.0

  • Software Version: 1.1.0 Build 20241224 Rel. 35085

    Please find the attached log for reference.

     

    Hardware Version: RE505X v2.0
    Software Version: 1.1.0 Build 20241224 Rel. 35085

    2024-01-01 01:16:43 dhcps:Sent an ACK packet to 192.168.1.200
    2024-01-01 01:16:43 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:16:40 dhcps:Received an inform packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:16:38 dhcps:Received an inform packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:16:29 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:16:15 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:16:10 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:16:05 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:16:03 dhcps:Sent an ACK packet to 192.168.1.200
    2024-01-01 01:16:03 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:16:02 locale:Language is changed to 'en_US'
    2024-01-01 01:16:02 locale:Explorer language is 'en_US'
    2024-01-01 01:16:00 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:55 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:51 locale:Language is changed to 'en_US'
    2024-01-01 01:15:51 locale:Explorer language is 'en_US'
    2024-01-01 01:15:46 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:35 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:25 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:22 dhcps:Sent an ACK packet to 192.168.1.200
    2024-01-01 01:15:22 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:15:22 dhcps:Provided an offer for the client with ip 192.168.1.200
    2024-01-01 01:15:22 dhcps:Received a discovery packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:15:21 dhcps:Provided an offer for the client with ip 192.168.1.200
    2024-01-01 01:15:20 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:15:19 dhcps:Received a discovery packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:15:19 dhcps:Sent an NAK packet
    2024-01-01 01:15:19 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:15:19 dhcps:DHCP server started
    2024-01-01 01:15:17 dhcps:DHCP server stopped
    2024-01-01 01:15:17 dhcpc:Sent a detection for DHCP.
    2024-01-01 01:14:49 locale:Language is changed to 'en_US'
    2024-01-01 01:14:49 locale:Explorer language is 'en_US'
    2024-01-01 01:14:41 locale:Language is changed to 'en_US'
    2024-01-01 01:14:41 locale:Explorer language is 'en_US'
    2024-01-01 01:14:00 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 01:14:00 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:09:35 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 01:09:35 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 01:04:06 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 01:04:06 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:57:27 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:57:27 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:55:28 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:55:28 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:53:27 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:53:27 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:52:27 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:52:27 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:48:27 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:48:27 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:42:39 locale:Language is changed to 'en_US'
    2024-01-01 00:42:39 locale:Explorer language is 'en_US'
    2024-01-01 00:42:25 locale:Language is changed to 'en_US'
    2024-01-01 00:42:25 locale:Explorer language is 'en_US'
    2024-01-01 00:42:03 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:42:03 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:24:09 locale:Language is changed to 'en_US'
    2024-01-01 00:24:09 locale:Explorer language is 'en_US'
    2024-01-01 00:24:01 locale:Language is changed to 'en_US'
    2024-01-01 00:24:01 locale:Explorer language is 'en_US'
    2024-01-01 00:23:52 locale:Language is changed to 'en_US'
    2024-01-01 00:23:52 locale:Explorer language is 'en_US'
    2024-01-01 00:23:29 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:23:29 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:16:39 locale:Language is changed to 'en_US'
    2024-01-01 00:16:39 locale:Explorer language is 'en_US'
    2024-01-01 00:16:18 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:16:18 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:16:02 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:16:02 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:16:02 dhcps:Provided an offer for the client with ip 192.168.1.131
    2024-01-01 00:16:02 dhcps:Received a discovery packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:15:47 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:15:47 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:03:44 locale:Language is changed to 'en_US'
    2024-01-01 00:03:44 locale:Explorer language is 'en_US'
    2024-01-01 00:03:36 locale:Language is changed to 'en_US'
    2024-01-01 00:03:36 locale:Explorer language is 'en_US'
    2024-01-01 00:02:55 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:02:55 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:02:55 dhcps:Provided an offer for the client with ip 192.168.1.131
    2024-01-01 00:02:55 dhcps:Received a discovery packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:02:21 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:02:21 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:01:51 dhcps:Sent an ACK packet to 192.168.1.131
    2024-01-01 00:01:51 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:01:51 dhcps:Provided an offer for the client with ip 192.168.1.131
    2024-01-01 00:01:49 dhcps:Received a discovery packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:01:49 dhcps:Sent an NAK packet
    2024-01-01 00:01:49 dhcps:Received a request packet from 50:96:5A:FF:1C:D4
    2024-01-01 00:00:01 dhcps:DHCP server started
    2024-01-01 00:00:00 time-settings:Service start
     

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Connectivity issue with TP-Link AX1500 in Access Point mode-Solution
2025-09-26 10:02:55 - last edited 2025-10-16 11:35:30

Hi @asishpmathew ,

Welcome to our community.

 

If you want to set the extender to be an Access Point, you only need to change the operation mode:

  • Click Mode in the top right corner of the page.
  • Select Access Point and click Save. The extender will reboot and switch to Access Point mode.

 

Please try the following suggestions:

1. Test the internet connection by connecting your client devices directly to the main router. This will help determine if it is specific to the RE505X or if it's a problem with the router itself.
2. Try using a different port or cable to connect the main router.

 

 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: △New Firmware Update for Archer BE260/Archer BE400 to Support VPN Merge, New ECO Mode, and More △Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN △Tether KidShield Test Recruitment - Safeguarding Children's Online Experience If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Connectivity issue with TP-Link AX1500 in Access Point mode-Solution
2025-09-26 10:02:55 - last edited 2025-10-16 11:35:30

Hi @asishpmathew ,

Welcome to our community.

 

If you want to set the extender to be an Access Point, you only need to change the operation mode:

  • Click Mode in the top right corner of the page.
  • Select Access Point and click Save. The extender will reboot and switch to Access Point mode.

 

Please try the following suggestions:

1. Test the internet connection by connecting your client devices directly to the main router. This will help determine if it is specific to the RE505X or if it's a problem with the router itself.
2. Try using a different port or cable to connect the main router.

 

 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: △New Firmware Update for Archer BE260/Archer BE400 to Support VPN Merge, New ECO Mode, and More △Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN △Tether KidShield Test Recruitment - Safeguarding Children's Online Experience If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
Recommended Solution
  0  
  0  
#2
Options

Information

Helpful: 0

Views: 364

Replies: 1

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.