@vmonkey 

I think that's trying too hard to explain their design choice.

If their target market won't choose AP mode then it makes even less sense that those folks who explicitly chose AP mode are silently surprised when a DHCP server pops up which is GUARANTEED to screw up their network and generate support calls.

In the last 4 years, no one has provided a valid example of why this feature does anything of use in a network with AP-configured wireless.

Show me another basic consumer-focused wireless product that when in AP mode fires up a DHCP server. tp-link know it's stupid to do this, as it's not replicated in their EAP range where AP mode is as dumb as it should be.

vmonkey wrote

While I am also affected by this issue (and I cannot disable it on m4 V2), I doubt it will ever be disabled by default. 

 

My understanding is that the deco series is by design meant for BFUs. As such, they lack many very basic settings, e.g., selection of WiFi channel. Most of BFUs probably do not use AP mode at all. And even if yes, TPlink might be worried of receiving support request for not being able to connect to the units because the external DHCP server failed.

 

Thus, I believe that the issue is actually elsewhere. It lies in the presentation of the Deco series by TP-Link, they should have mentioned explicitly not only what are they good for, but also what are their limitations due to the design (of course, they can link to their other products). But since this was not (and probably has not) been done, I feel that we are all trapped by this bad decision.

Just found this forum and it seems to explain a lot of the conflicting IP address problems I seem to be having with my newly installed S7 AC1900.

I recently upgraded to Vodafone Hi-Speed fiber and of course, received a new Vodafone router which I set up as the primary DHCP server for my network together with a fixed IP pool.  At first, things went fine but then I decided to upgrade my old S4 Wi-Fi network which was limited to 100 Mbits and purchased the S7 AC1900 set which were set up as access points. 

It did not take long for everything to start falling apart, especially my embedded IOT devices many of which had fixed IP addresses from the reserved pool.  I have spent a week desperately trying to figure out why my reserved pool (as defined in my router's DHCP section) was getting corrupted and kept giving IP conflict messages.

Finally, in desperation, I switched off the S7 AC1900 as it was as far as I could see the only thing I had changed.  Immediately the problem disappeared so I assumed the S7 had been giving out IP addresses despite being set as an Access point.  

Although I have not seen the S7 AC1900 specifically mentioned in the forum I assume it has the same (stupid) smart DHCP system.  Can anyone confirm this and is there a firmware update that fixes it?

If not, it is going back to Amazon as it is useless to me.

  @Purclewan 

This is also a problem—no formal mention of this dumb feature in the primary product documentation.

Save yourself time and energy, return it to Amazon and go with something else.

I also have this problem, it is so annoying and I am not able to use the Deco M4. Every day or so the M4 DHCP server starts up and allocates the incorrect IP addresses.

For me all was ok until I foolishly upgraded.

I have had them too long for a refund. I will have to spend more money on a better product, it will not be TP link that is for sure.

I also just got stuck in this stupid DHCP problem at work, luckily in the system of 8 DECO E4 I got a few DECO E4 V4 that just updated the Smart DHCP button, and everything was resolved.

I’m lucky I don’t have to endure this for years like you guys.

I just stumbled across this Smart DHCP undocumented feature a few days ago.  The documents clearly state that several features - including the DHCP server - are disabled for AP mode in my M4 V2, so whose bright idea was it to add another hidden DHCP server that was fairly obviously going to lead to network instability?  I've wasted a couple of days on this problem and still not managed to recover the situation completely.  Will definitely be looking to replace these units.

IanMK wrote

I just stumbled across this Smart DHCP undocumented feature a few days ago.  The documents clearly state that several features - including the DHCP server - are disabled for AP mode in my M4 V2, so whose bright idea was it to add another hidden DHCP server that was fairly obviously going to lead to network instability?  I've wasted a couple of days on this problem and still not managed to recover the situation completely.  Will definitely be looking to replace these units.

  @IanMK 

You should be able to turn off DHCP server running in AP mode after installing firmware from that link: Deco M4/S4_V2 Support Connection Preference

You may only need to install that firmware on Main Deco.

  @Alexandre. 

Thank you.  I'll try this when I get a moment.  This fix needs to be published in a formal release as soon as possible.

I also have this problem, it is so annoying, everything was working before I upgraded the firmware and it messed up my network. My router reboot frequently because of it, if I disconnect them, no more problem. I have had them too long for a refund and would not have chosen TP Link if i knew it would cause such issues. Please fix it !