How does one completely disable the DHCP server on TL-WR802N? You would think with LAN Setting->SmartIP(DHCP). Though you don't. Here is why: when you set it to DHCP, and it gets an address offer, all is fine. If it doesn't get one, or no renewal, it automatically starts its own DHCP. I don't want this. I don't want it starting its own DHCP when it is without IP. Consider this 'smart' or not. 

Here is the full backgound: we run one TL-WR802N in Operation Mode 'Client' and with 'SmartIP(DHCP)' to hook an RJ45-only-box to an AP. This AP is connected to the main, and unique, DHCP server through a WiFi link. Once this link goes down, the clients won't obtain/renew DHCP. Bad luck, and we are aware of that. 

However, when this TL-WR802N doesn't get/renew an IP due to the missing WiFi link, it does - so it seems - inevitably start its own DHCP, dishing out its own IPs. Inevitably, the other clients then accept the IPs dished out through this rogue behaviour. Meaning, they won't reach beyond that access point, because the TL-WR802N considers itself as gateway in case of dishing out IPs.

The DHCP Settings are grayed out, and it is written in red: "Note: The DHCP Settings function cannot be configured if you have chosen Smart IP (DHCP) in Network->LAN (in this situation the device will help you configure the DHCP automaticaly as you need)." So, this is intended, and there seems to be no way to completely disable the DHCP server.

It made me quite angry when I finally understood this reason for regular network outages of the clients connected to this AP. It could have never imagined when I configured it, that it would either have an IP - or respond to DHCP REQUESTS. 

Is it asked too much to want to be able to just configure it to be a mere DHCP client; and never turn into a DHCP server?

Would anyone have a solution to avoid this not-too-smart behaviour, please?

Btw. This is intended behaviour, as can be seen from this log entry:

I consider this a bug, yes, because it is run as CLIENT and not as AP.