My Rachio is working as expected and I have no problems accessing it with the app. An issue I have with it is it’s constantly doing DHCP to my router as seen in the below logs. I have the lease time on my LAN subnet set to 7 days.
I’m wondering why it’s doing this?
TIA
Sep 12 14:00:13 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:00:13 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:13 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:13 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:24 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:00:24 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:24 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:24 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:35 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:00:35 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:35 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:35 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:43 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:00:43 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:43 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:43 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:54 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:00:54 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:54 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:00:54 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:05 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:05 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:05 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:05 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:13 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:13 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:13 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:13 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:24 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:24 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:24 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:24 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:35 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:35 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:35 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:35 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:45 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:45 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:45 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:45 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:56 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:01:56 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:56 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:01:56 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:07 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:02:07 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:07 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:07 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:15 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:02:15 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:15 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:15 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:26 dnsmasq-dhcp[479]: DHCPDISCOVER(br0) 0c:2a:69:0b:00:5c
Sep 12 14:02:26 dnsmasq-dhcp[479]: DHCPOFFER(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:26 dnsmasq-dhcp[479]: DHCPREQUEST(br0) 192.168.1.190 0c:2a:69:0b:00:5c
Sep 12 14:02:26 dnsmasq-dhcp[479]: DHCPACK(br0) 192.168.1.190 0c:2a:69:0b:00:5c
franz
September 13, 2015, 10:33pm
2
I’ve opened a ticket with our WiFi provider and will forward along any information.
Thanks!
franz
September 14, 2015, 2:39am
3
Here is the response from our WiFi provider…are you still seeing this behavior?
That’s strange. Generally DISCOVER is only sent at a reconnection (wifi down, wifi up), but I don’t see large numbers of reconnects for that device - 3 in the last 24h, and I looked back a week to cover the 12th and it’s the same story.
If it was a DHCP lease timeout then we’d see it REQUEST not DISCOVER.
Can you ask the user if it’s still doing this?
It is still doing it. Looking at my router log, it’s doing the DHCP DORA process roughly 3 times a minute constantly.
franz
September 15, 2015, 5:56am
5
Thanks, I’ve relayed this information.
I am having the same issue with my router (Asus RT-AC66R) with the constant DHCP processes in the log.
Also, I reserved IP address 192.168.1.101 for the Rachio Iro. After some time, the device goes offline and I have to power cycle the Iro to get it to reconnect. If I don’t do this, I am unable to access the device through the app on my smartphone.
franz
September 15, 2016, 7:31pm
7
@terrierl
We opened a ticket with our Gen 1 WiFi provider regarding this controller, questions below.
As in, it’s dhcp’ing constantly? Can he provide any logs?
We wouldn’t be able to see any activity pre connect in our logs
Thank you for looking into this so quickly. See below for what it looks like.
Sep 15 12:54:23 dnsmasq-dhcp[2833]: DHCPDISCOVER(br0) 0c:2a:69:0b:08:18
franz
September 16, 2016, 3:05pm
10
@terrierl
New firmware was applied to your controller by our third party vendor, we can see if that helps the issue.
Thank you. I will report back with results. I am using custom firmware for the Asus router, Merlin’s build, which has been rock solid for everything but the Rachio.
franz
September 16, 2016, 3:32pm
12
@terrierl
Are you seeing the DHCP stuff now?
Yeah, I can see that the stale connection hung around for a bit before it was timed out. Can you check with the customer to see whether he’s seeing the DHCP stuff now?
This was earlier and it appears the DHCP lease is active according to the information below this log:
Sep 16 10:54:13 dnsmasq-dhcp[664]: DHCPDISCOVER(br0) 0c:2a:69:0b:08:18
DHCP Leases
So far so good…What firmware update was applied? Was it a beta version?
Hopefully that did the trick.
1 Like
I figured I would check it again and this is what I came across in the log today. Not good…this has been going on since 5am this morning from the log, but I could not post all of it due to the length.
Sep 19 12:00:18 dnsmasq-dhcp[2166]: DHCPDISCOVER(br0) 0c:2a:69:0b:08:18
Hi, I’m from the company that made the module/OS that does the networking in your device.
Can you tell me your timezone so I can relate your logs to our logs? The device is staying connected just fine from what I can see, but seems like the DHCP client thinks you have a very short lease… or something.
Can you take packet captures of this traffic?
Could you also clarify which version of Merlin’s build you’re running and the exact router? The Merlin’s website doesn’t list the RT-AC66R as a supported device, only the RT-AC66U.
1 Like
Thank you.
It’s the latest stable version of merlin’s build 380.61, but it has been doing this since the earlier builds as well. The firmware works on both the R and U variants according to Merlin’s site so I know it’s not a compatability issue with the firmware. See here towards the bottom. I have the RT-AC66Rhttp://asuswrt.lostrealm.ca/about
I am in Eastern time zone.
As far as the packet capture I will work on getting this over to you when I am able to.
Thanks - if you have tcpdump installed you should just need to do something like:
sudo tcpdump -w /mnt/capture.pcap host 192.168.1.101
This will dump all traffic to and from the Rachio and the router; ideally do this when it’s going mad, but if you can’t get that at first then starting this command then power cycling the Rachio will give us some information about the DHCP responses being sent.
If all else fails we’ll try to get hold of one of those devices & load the same SW revision you have. We have an RT-N56U but that’s a tiny bit too old to be supported
2 Likes
Thanks again. I will try to get to this tonight. The AC66R is getting old itself, but has probably been the most solid router I have owned.
