Plume, DHCP issue on hEX

RouterOS General
1

My Plume network worked fine, installed the new SuperPod and now it will not keep an IP.

See attached log.

I have tried making the lease static, no help.

Any ideas?

BTW it works fine using DHCP from a Linksys router.

Thanks

Adam
Tik and Plume DHCP.PNG

2

That looks more like the device can’t communciate with something somewhere (external server etc) and so it bounces its stack every 20 seconds to try and re-establish a connection (eventually it does a complete reset which is where you see the port drop) as a last resort. I see this a lot with Nest cameras doing the same thing.

2 options spring to mind;

  1. are you using the DNS server/cache on the hEX? There are a couple of IOT vendors that use some responses that for some reason don’t work on the HEX DNS. To prove this, temporarily change the DNS the dhcp gives out to 8.8.8.8 or 1.1.1.1 and see if that helps.

  2. something in the firewall config is preventing a connection / config the plume is trying to validate. Not sure if it’s using uPNP etc but you might want to check the connections tab in the firewall , or next step would be grabbing a packet trace to see which upstream connnection is failing.