@TP-Link I updated the firmware of my re205 and it enabled the options for dhcp. I have tried 2 options for client dhcp assignment.

1. Disable dhcp on RE205 and make it assign by my router.

2. Enable the dhcp on RE205 and keep the range equal to the router or subset of the router.

Both cases I do get an IP assignment problem when I do a reboot of the client and the solution is to reboot the RE205 or router which is quite annoying.

I do tried to assign a static ip to the client from the dhcp range and even out of it but belonging to the same network. But still the issue is there. If I reboot the client it cannot reach the router until a reboot is done on either router or RE.I have also kept the band same on router and RE.

What I noticed after the reboot of the client is that the client can ping to the nearby hosts in the network but not to the router even though all are in the same local network/subnet. At the same time the non-rebooted client can ping the router. A wireshark check in client shows the client broadcasting asking for the router to respond but this broadcast seems not being reached to the router even though all other clients can reach the router through RE.

On a linux client when I assigned a unique static ip beyond the dhcp range but belonging to the same network/subnet it alerts for duplicate IP when I do a ping to router. I don't know why it is behaving like this.

Do you have any other configuration setting to reach the router on RE?

Also is there a limitation for RE where it can't forward the broadcast from client to the router? Any settings to modify?

Current RE update firmware version

1.0.2 Build 20201030 Rel. 40667

RE205 v3.0

Router M7350

1.1.2 Build 201019 Rel.1077n