Deco M9 Plus in AP mode taking over DHCP server and assigning IPs in own subnet
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
After installing the M9 in access-mode in my network, I notice some devices cannot be reached anymore.
When examining the situation I notice that the IP the devices get is in the range the M9 uses when in router mode.
When switching to Router-mode, the (internal)M9 IP is: 192.168.78.1 and the DHCP range it uses is from 192.168.78.100 to 192.168.78.200 with a subnet of 255.255.255.0.
Router mode is unusable in my situation, so I'm forced to use the AP-mode.
Some devices (like a "Wemos D1" board, a Thermostat and sometimes my printer when turning it on) get an IP in the 192.168.78.x range while my
cable-modem (Lan Gateway with IP: 192.168.178.1 and subnet 255.255.255.0) is setup to handle the DHCP with a range of 192.168.178.30 - 192.168.178.250 .
The weird thing is that the cable-modem is UP all the time when one of these devices is added, but still doesn't get an IP from my Modem and because of the
different subnet, can't see the device. The device says it's up and running on the SSID from the Deco M9, with the Deco M9 given IP.
From within the Deco App, the device can be seen WITH the wrong IP address....
Because the devices it happened to are headless and no monitor can be attached, looking at the network from the device is not possible.
For some reason the Deco M9 DOES listen AND responds to DHCP requests in certain situations,
making networking a real challenge, even for someone with a good background in networking!
I hope someone will fix this serious flaw in the firmware...
I'm not the only one experiencing problems with DHCP in AP-Mode accordig to several other posters on the community.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Sorry to hear you are always having issues. Issues that tplink ( @Kevin_Z @tplink ) don't think deserve a fix in almost 12 months.
That is what makes the least sense to me. All they have to do is offer a toggle in advanced settings to disable "Smart DHCP" for people experiencing this issue. Yet, it never comes.
Speaks volumes about the respect they have for paying customers. I am slowly replacing my network kit and will offload the tplink mesh devices and switches and never go back to this brand.
- Copy Link
- Report Inappropriate Content
Yup, hopefully a simple 'disable smart DHCP' switch will do the trick...
HELLO TP-LINK ! Please remove this infuriating, network killer fault... on an otherwise fantastic product...please!
- Copy Link
- Report Inappropriate Content
I have exactly the same problem. It happens too often to make me upset. My DECO in AP mode takes DHCP role and mess up my network. I do not want to switch into router mode, because I have a good router I want to keep. I am not sure I can trust DECO M4 security in router mode.
So yeah, I would appreciate the patch from TP LINK soon as well.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
wow. just wow.
Havng just discovered this problem with my Deco Mesh M5s, and reading all the threads about it I'm extremely disspointed in TPLink for providing what can only be described as broken, not fit for purpose equipement.
I am packing my DECO's up right now, sending them back and NOT purchasing ANYTHING from TPlink again.
Just terrible, absolute garbage. I'm sorry I wasted my time with them . Disgusting.
- Copy Link
- Report Inappropriate Content
So a new firmware gets released and there is no sign, NOTHING, about being able to disable the "Smart DHCP" feature.
Wow. After 10 months of this being reported as a problem.
Hopefully, I am wrong. Please can you confirm either way.
Please show some respect to your customers.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I think they do. Look at many of the recent forum topics where tplink have responded.
They've perhaps given up on this, and the topic in general as it seems after 10 months of knowing about it they've decided not to address in their latest firmware update.
It's a sign to me of their commitment to the product at its core and to the customers who paid good money for it.
It's the reason I won't buy another tplink product in the future.
- Copy Link
- Report Inappropriate Content
Maybe we should, instead of adding to this thread, simply start flooding the forum with a new thread everytime?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 49228
Replies: 124
Voters 6
