Dhcp assign very poor

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Dhcp assign very poor

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Dhcp assign very poor
Dhcp assign very poor
2023-07-13 18:59:10
Model: TL-WA1201  
Hardware Version: V3
Firmware Version: 1.10.32 Build 221020 Rel.61052n(4555)

Ciao a tutti , utilizzo un tplink tlw1201 come ripetitore wifi di un altro AP

TP-Link Wireless N Access Point WA801N 

 

Downstream of the 1201 network everything works, but the release of the dhcp by the firewall connected on the 801n is very slow. I tried with a client to connect not to the 1201 but directly to the 801n and it works regularly and the ip release is fast. In short , after 1201 however , the ip addresses are assigned but with a strong delay .

 

  0      
  0      
#1
Options
2 Reply
Re:Dhcp assign very poor
2023-07-14 08:26:22

  @frankz66 

 

Hi,

 

WA801N is an access point as well, similar as the TL-WA1201, may I know the topology of your network?

And is there a router in front of the WA801N? If so, please try to connect the TL-WA1201 to the router directly and test if there is the same issue.

 

In addition, please make sure the DHCP server is disabled on the TL-WA1201 access point, the DHCP Server should be still on your main router.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. 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.
  0  
  0  
#2
Options
Re:Dhcp assign very poor
2023-07-15 19:35:30
Thank you for replying . one of the segments of my pfsense firewall is a card dedicated directly to the tl 801 which as previously written transmits an essid xxxx . This essid is relaunched by tl 1201 which downstream of the latter is connected to a series of hosts. Chiaraemnte the dhcp is active only and exclusively on the pfsense. The problem arises only after 1201 or rather the assignment of the ip is very slow. I tried to connect a client before 1201 then to 801 and it works on a regular basis for ip assignment. Describing my topology is a bit complicated as I have a cluster with 3 nodes in Ha and one of the main virtual machines is the pfsense .
  0  
  0  
#3
Options