Deco M9 Plus in AP mode taking over DHCP server and assigning IPs in own subnet
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
Yeah it's a big pain. But the Chinese don't give a sh1t. They'll just tell you to 'watch the app!' and be done with it.
- Copy Link
- Report Inappropriate Content
Hello, everyone,
I might have found a solution.
TLDR: disable smart DHCP by assigning a static IP and disabling the DHCP server in every AP you have. This you do in the AP's. It does not work if you reserve the IPs to the AP's in the router and leave dummy DHCP on.
I bought an Archer C6 to route in my house 1.5 years ago. I used many of its features (VPN, VPS, etc) and everything went smooth all that time, except for the guest WIFI signal that kept dropping so I decided to shut it off as I have not so many guests at home anyway.
A week ago there was one shortage and I was not home. My wife tried restarting the C6 but she could not make it work. There had been many other shortages but this one apparently killed my router. When I came home I couldn't not even connect to the router with its IP or address. The app Tether allowed me to connect but soon after got me out again and lost the visibility of the router.
I went and bought a TP-Link TL-R600VPN to have a little more flexibility and put it to work. Everything went smootly again. Then, I connected an AP TP-Link TL-WA901ND and worked fine as well. A couple of days later I replugged the Archer C6 and tried re connecting to it. Maybe I could use it as an AP too. I noticed its IP had changed to 192.168.0.254 after the power outage. I logged in with the old password I had set up and voila, it worked. I was in. I switched to AP mode and everything worked normally.
Here is when finally I encuntered (noticed) the dreaded Smart DHCP / IP range problem. The basic TL-WA901ND was dropping all connections every 10 minutes. I tried restarting but nothing was fixed. I then went to the router and reserved an IP to the TL-WA901ND, thinking that maybe the TL-WA901ND was losing its IP every now and then. Failure.
I then tried turning on the DHCP sever on the TL-WA901ND AP and allocated an exclusive range of IPs for it, on the router. The AP allocated ONE IP and then the router's (the TL-R600VPN) DHCP server took over allocating all other devices connected to it. Again, dropping them every couple of minutes.
I decided to return to smart DHCP on the TL-WA901ND AP and erase the IP reservation for it in the router. Finally it ocurred to me to use an static IP in the AP TL-WA901ND, while leaving the router without an IP reservation. Problem solved. At least for the last 3 hours.
I checked the logs in my TL-R600VPN and lo and behold, it was assigning the same IP over and over to my other AP (the Archer C6). Every 5 seconds or so, the router was giving the AP the same IP. I then changed the Smart DHCP function on the Archer C6 to static IP, and then the router stopped giving the same IP to the Archer C6 every 5 seconds. As far as I am concerned, my network is stable now.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
You can assign a static IP to the AP on the advanced options. Right in WAN settings.
- Copy Link
- Report Inappropriate Content
Please share screenshots specific to the M9.
There should be no WAN option when in AP mode, which confuses me a little. I have looked both in the Deco app and also via the web link to the settings direct on the APs themselves.
I see no way at all to add a static IP address.
- Copy Link
- Report Inappropriate Content
@RodrigoBG8 If I understand your solution correctly, your main router is the TL-R600VPN which is managing DHCP. In that you have configured a static IP for your APs which are TL-WA901ND and Archer C6? Or have you set a static IP in the APs?
- Copy Link
- Report Inappropriate Content
I stand corrected. Instead of you can, I must have written you should be able to.
I don't have a Deco M9 AP and there are no simulators around in the TPL site. I only saw the user's manual here, in page 25
- Copy Link
- Report Inappropriate Content
I set the static IP's directly in the AP's.
I am yet to test that concurring with the IP reservation and mac binding in the Router.
Sadly, after some more hours, the AP TL-WA901ND dropped the connections again, and on the router's log I could see the DHCP giving the AP TL-WA901ND the same IP three or four times in 3 minutes.
Maybe when I reserve the IP on the router things will improve. Maybe not. In any case, I'll be waiting for an upgrade as well as you.
- Copy Link
- Report Inappropriate Content
The dumb DHCP activated itself in the TL-WA901ND...
That's what caused the AP severing connections again. Now I'll set a static IP in the AP and reserve the same IP in the router. I'll keep you posted.
- Copy Link
- Report Inappropriate Content
The manual refers to setting a static WAN interface on the M9s.
However this thread is about the M9s in AP mode, i.e. having no WAN interface.
The model you're talking about is something totally different and it might be worth starting your own thread rather than confusing/hijacking this one 👍
Appreciate you looking though.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 54976
Replies: 123