Conflicting DHCP when Deco in AP mode ?

Conflicting DHCP when Deco in AP mode ?

151 Reply
Re:Conflicting DHCP when Deco in AP mode ?
2021-12-09 13:16:44

 

TP-Link wrote

@Jay_Jay 

Hi, I see that you also have Deco M5 which Is on firmware 1.6.0.

So when Deco M5 is working as the main Deco under access point mode, there is no need to install any beta on M4.

You could turn off the smart DHCP switch on M5, then M4 will sync with the same configuration.

Thank you.

@TP-Link

 

Ok, good to know. Thank you.

  0  
  0  
#85
Options
[Feature Request] Smart DHCP on/off switch under access point mode
2022-02-04 15:44:40
This is still broken as I have a functional DHCP server in my network and "Smart" DHCP refuses to remain disabled. It is causing my network to be practically unusable because it keeps stepping over my real DHCP server. For this product to be useable for those of us who run a real DHCP server (there's a ton of us, clearly) this feature needs to have an option to completely disable. I don't want it to ever come on unless I turn it on, why is that such an impossible concept for the developers to grasp?? Just let me turn it off, and while you're at it, let me set whatever WiFi channel that I want to use! I paid $500 for a WiFi system that I expect to be able to use. It is unusable. That price point comes with a certain expectation of control, and the power users currently have zero control. I have two x90's at the latest firmware in AP mode. Just want DHCP disabled indefinitely and the ability to select my WiFi channels. My DHCP server is serving a limited scope of IP's to my network, leaving about half of the range for static IP's. I suspect perhaps this is why "Smart" DHCP is failing at its job. Maybe it doesn't play well with limited DHCP scopes in the environment? Whatever the case, the correct resolution would be to remove the "smart" feature and just leave it off if the user turns it off. It really is maddening!!
  1  
  1  
#87
Options
[Feature Request] Smart DHCP on/off switch under access point mode
2022-02-04 15:50:36 - last edited 2022-02-04 15:52:22

@Wraith.DJ 

 

I hate to point out the obvious but you're wasting your time. This issue is now close to 3 years old. The ability to fully disable a network breaking and undocumented feature should have come within months of the initial post. But 36 months in, it's still not here.

 

I'd say move off of tp-link altogether but I am using, and like, their Omada product line for my APs (EAP660 HD), and they work great. I suspect it's an entirely different product team

 

Sell the stuff you've currently got and find something better.

  1  
  1  
#88
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-02-10 15:27:07

Can someone who has tried v1.6 / a beta confirm whether the new "disable smart dhcp" function works properly? I have a collection of M9s and am very frustrated by this. I'm trying to decide whether to just get rid of my M9s or wait it out a little bit longer in hopes that a 1.6 firmware will drop soon. It's a moot point if the feature to disable it doesn't work properly.

  0  
  0  
#89
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-03-12 20:12:56

  @GPGeek 

There is no such thing as a master dhcp server. Every dhcp server will answer a DHCPDISCOVER request if it has a free lease. It is entirely up to the client to decide which lease to request (DHCPREQUEST). The protocol doesn't specify how the client makes its decision. I stumbled on your post while looking for a dhcp problem I have with my Deco M5. It stops relaying answers from my dhcp server.

 

Deco M5 Firmware 1.5.7 Build 20210819 Rel. 43499

 

dhcp server log:

...

Mar 12 12:25:34 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:34 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:40 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:40 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:49 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:49 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:51 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:51 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:54 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:54 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:59 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:25:59 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:26:05 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:26:05 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1

 

Reboot closest Deco M5

 

Normal sequence {

Mar 12 12:46:25 nuc dhcpd[689803]: DHCPDISCOVER from f0:f0:a4:53:17:bf via eno1
Mar 12 12:46:25 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1
Mar 12 12:46:25 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.151 (192.168.68.8) from f0:f0:a4:53:17:bf via eno1
Mar 12 12:46:25 nuc dhcpd[689803]: DHCPACK on 192.168.68.151 to f0:f0:a4:53:17:bf via eno1

}

Mar 12 12:47:40 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.163 from 08:84:9d:77:8b:ed via eno1
Mar 12 12:47:40 nuc dhcpd[689803]: DHCPACK on 192.168.68.163 to 08:84:9d:77:8b:ed via eno1
Mar 12 12:47:44 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.37 from 04:0c:ce:e3:65:fe via eno1
Mar 12 12:47:44 nuc dhcpd[689803]: DHCPACK on 192.168.68.37 to 04:0c:ce:e3:65:fe via eno1

Rebooted Deco M5 requesting an IP address {

Mar 12 12:47:53 nuc dhcpd[689803]: DHCPDISCOVER from 3c:84:6a:98:53:e4 via eno1
Mar 12 12:47:53 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.10 to 3c:84:6a:98:53:e4 via eno1
Mar 12 12:47:53 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.10 (192.168.68.8) from 3c:84:6a:98:53:e4 via eno1
Mar 12 12:47:53 nuc dhcpd[689803]: DHCPACK on 192.168.68.10 to 3c:84:6a:98:53:e4 via eno1

}
Mar 12 12:48:22 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.52 from b8:27:eb:ef:d0:11 via eno1
Mar 12 12:48:22 nuc dhcpd[689803]: DHCPACK on 192.168.68.52 to b8:27:eb:ef:d0:11 via eno1
Mar 12 12:48:24 nuc dhcpd[689803]: DHCPDISCOVER from 40:a9:cf:64:0e:a3 via eno1
Mar 12 12:48:24 nuc dhcpd[689803]: DHCPOFFER on 192.168.68.152 to 40:a9:cf:64:0e:a3 via eno1
Mar 12 12:48:24 nuc dhcpd[689803]: DHCPREQUEST for 192.168.68.152 (192.168.68.8) from 40:a9:cf:64:0e:a3 via eno1
Mar 12 12:48:24 nuc dhcpd[689803]: DHCPACK on 192.168.68.152 to 40:a9:cf:64:0e:a3 via eno1

...

  2  
  2  
#90
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-03-14 09:56:14

  @ptimmons 

Hi, in case of any misunderstanding since I wasn't good at reading logs, could you please help me confirm the following details:
1.Deco is working on the access point mode,right?
2.what you are trying to say, the client sent the DHCP request and main ISP router answered, but Deco in between did not relay DHCP answers from main router to clients?
By the way, May I know the model number of your main router?
Can I have a full picture of your network layout?
Thank you very much.

 

  0  
  0  
#91
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-03-26 06:42:12 - last edited 2022-03-26 06:50:39

Hi,

 

just to be sure i understood correctly... i have 4 M4 in AP and Ethernet Backhaul.

My will is now to get rid of the DHCP server from the box, so i can change ISP with full transparency....

 

If i buy a M5, add it to the 3 M4, make it as main, and activate smart DHCP on it, it will sync to all Deco, even the M4 not having the smart DHCP (cause being on old firmware), and i can shut down DHCP server from my box.

 

Have I understood correctly ?

 

Edit : rereading the posts, i'm not sure i understood.... moreover, it is not interesting for me i think, as i need the M4 play DHCP server role, but need to be able to create static IP for some devices.... so not sure it will help, i need a router between my box and the M4 to play this role I guess.... but this is another box... and can find anything cheap, small, for that...

  0  
  0  
#92
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-06-13 00:23:03

  @David-TP 

 

I replied to the notification email but apparently the response didn't get forwarded to the list. Here is my original response:

 

Here are the requested details (and then some):

Switch is a tp-link t1600g-28ts 3.0 with software version 3.0.6 Build 20200805 Rel.55968, flash version 1.3.0 with 802.1Q vlans 1 untagged and 591 tagged, dhcp service/relay/L2 relay/filter disabled.
Router is Cisco RV325 with latest firmware (v1.5.1.13 (2020-10-27, 13:37:43)) with ip address 192.168.68.1, dhcp is deactivated, directly connected to t1600g-28ts port 24.
DHCP server is directly connected to t1600g-28ts port 8 native vlan 1 with address 192.168.68.8, CentOS 8 ISC DHCP.
3 x Deco M5 in AP mode, firmware 1.5.7 Build 20210819 Rel. 43499.
    deco M5 Main directly connected to t1600g-28ts on port 21 with ip address 192.168.68.10 obtained via dhcp, native vlan 1 and tagged vlan 591 for guest network.
    deco M5 Living room directly connected to t1600g-28ts on port 23 with ip address 192.168.68.11 obtained via dhcp, native vlan 1 and tagged vlan 591 for guest network.
    deco M5 Office connected to a tp-link tl-108ge 5.0 switch, firmware 1.0.0 Build 20191021 Rel.53360 on port 7 with address 192.168.68.12 obtained via dhcp, native vlan 1 and tagged vlan 591 for guest network.
tl-108ge port 8 directly connected to t1600g-28ts port 22, native vlan 1 and tagged vlan 591 802.1Q for guest network.
client is an Amazon blink camera with latest firmware, MAC address f0:f0:a4:53:17:bf attempting to get an ip address from the dhcp server, associated to Deco Main ssid "Wall-e" (2.4GHz and 5GHz) when the problem occured.

Network traffic captured from dhcp server. We can see the DHCPDISCOVER and the DHCPOFFER but no DHCPREQUEST. So either the DHCPOFFER or the DHCPREQUEST is not relayed or the client didn't DHCPREQUEST the DHCPOFFER.

Rebooting Deco M5 Main solved the problem. The problem has occurred a few times.

 

  0  
  0  
#94
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-06-13 02:17:51

  @David-TP 

 

There is one scenario I can think of that would involve the router. I will make the appropriate setup later this week and see if I can reproduce the problem. This time I will capture the traffic from the t1600g-28ts by mirroring the Deco ports (gigabitEthernet 1/0/21-23) to a network analyser (on gigabitEthernet 1/0/1). I'll open a ticket if I find that the router is not at fault.

  2  
  2  
#95
Options
Re:Conflicting DHCP when Deco in AP mode ?
2022-06-13 11:34:57

  @ptimmons 

Thank you very much and that would be very helpful.

By the way, the official firmware 1.6.0 for Deco M5 has been released today and it supports turning off DHCP on AP mode.

Maybe you could try to update to the latest version and turn off the DHCP first.

Deco M5_V3_1.6.0_220525

 

Thank you very much.

Best regards.

--------------------------

Deco X50-PoE is ready for your advice. If you are interested, please help us complete the following survey.

Deco X50-POE Survey

  0  
  0  
#96
Options