I use an L3-5M-P and it connects to my WIFI network, but it cannot connect to the eWeLink servers. My WIFI is using a router (192.168.1.1) that acts as the default gateway and a NUC (192.168.1.2) that acts as the DHCP server and DNS server. To ensure that my DNS doesn’t cause any issues, I have set the DNS for this device to 220.127.116.11 and 18.104.22.168.
This is the actual DHCP response that is sent to the device (192.168.1.143):
10:34:14.463626 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 333) 192.168.1.2.67 > 192.168.1.143.68: [udp sum ok] BOOTP/DHCP, Reply, length 305, xid 0x177804d4, Flags [none] (0x0000) Your-IP 192.168.1.143 Client-Ethernet-Address d0:27:02:f7:b5:66 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: ACK Server-ID (54), length 4: 192.168.1.2 Lease-Time (51), length 4: 3386 Subnet-Mask (1), length 4: 255.255.255.0 Default-Gateway (3), length 4: 192.168.1.1 BR (28), length 4: 192.168.1.255 Domain-Name-Server (6), length 8: 22.214.171.124,126.96.36.199 Domain-Name (15), length 19: "int.ramondeklein.nl"
I am able to ping the device, but it keeps flashing twice per second and is shown as “offline” in the eWeLink portal.
When I disable the DHCP server on 192.168.1.2 and enable the DHCP server on my router, then it connects immediately. In that case the IP address, DNS server and default gateway are 192.168.1.1.
There must be something wrong with how the L3-5M-P handles these DHCP settings (they work on all my other devices). I guess the L3-5M-P can’t deal with receiving an IP address from a DHCP server that is has a different IP then the default gateway.
Does anyone have a suggestion how to deal with this?