Menu
What's new
By:
Filters Better Search

Desperately Requesting Assistance: Honeywell Redlink Internet Gateway [Happening Again]

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

agilis said:
Device has been connected to my neighbor's router, RT-AC86U for over 2 hours without any issues.
Click to expand...
Strange. But then it did work for you up until you made the first change to the configuration. Can you see what version of the firmware he's using?
 
ColinTaylor said:
Strange. But then it did work for you up until you made the first change to the configuration. Can you see what version of the firmware he's using?
Click to expand...

The version on their router is the following:

Version 3.0.0.4.384.82072
2020/08/17

I tried this firmware version last night :/
 
Last edited:
agilis said:
The version on their router is the following:

Version 3.0.0.4.384.82072
2020/08/17

I tried this firmware version last night :/
Click to expand...

How old is your AC86U? 2018 China?

OE
 
I think that the DHCP messages you saw when you switched to Merlin's firmware has given more clarity on the problem. I believe that those messages are suppressed by default in the stock firmware which is why you hadn't seen them before. Although this still doesn't explain why it worked at your neighbour's with the same hardware and firmware.

We had suspected that it was a DHCP issue. It appears that even though the RIG is asking the router for an IP address (DHCPDISCOVER) it is deaf to the reply that the router is sending it (DHCPOFFER). There are two ways the DHCPOFFER can be sent to be RIG which should be indicated by the RIG itself, broadcast and unicast. It's possible that RIG is not following the correct procedure here. As an experiment you could try logging into the router via SSH and issuing the following temporary commands:
Code: 
killall dnsmasq
dnsmasq --log-async --dhcp-broadcast
Test the RIG by turning it off and on again. Does it get an IP address straight away?

Reboot your router to undo the change you made.
 
ColinTaylor said:
I think that the DHCP messages you saw when you switched to Merlin's firmware has given more clarity on the problem. I believe that those messages are suppressed by default in the stock firmware which is why you hadn't seen them before. Although this still doesn't explain why it worked at your neighbour's with the same hardware and firmware.

We had suspected that it was a DHCP issue. It appears that even though the RIG is asking the router for an IP address (DHCPDISCOVER) it is deaf to the reply that the router is sending it (DHCPOFFER). There are two ways the DHCPOFFER can be sent to be RIG which should be indicated by the RIG itself, broadcast and unicast. It's possible that RIG is not following the correct procedure here. As an experiment you could try logging into the router via SSH and issuing the following temporary commands:
Code: 
killall dnsmasq
dnsmasq --log-async --dhcp-broadcast
Test the RIG by turning it off and on again. Does it get an IP address straight away?

Reboot your router to undo the change you made.
Click to expand...

I did as you asked. Sorry it took so long. I needed to wait for permission from neighbor to go inside so I could remove the device from their network.

I logged into the router and issued the command and then I plugged in the device. This is what I'm seeing in the log:

Code: 
Nov  6 18:57:47 dnsmasq-dhcp[2845]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov  6 18:57:47 dnsmasq-dhcp[2845]: DHCPOFFER(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb
Nov  6 18:57:47 dnsmasq-dhcp[2791]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov  6 18:57:47 dnsmasq-dhcp[2791]: DHCPOFFER(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb
Nov  6 18:57:48 dnsmasq-dhcp[2845]: DHCPREQUEST(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb
Nov  6 18:57:48 dnsmasq-dhcp[2845]: DHCPACK(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb Gateway7C8CEB
Nov  6 18:57:48 dnsmasq-dhcp[2791]: DHCPREQUEST(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb
Nov  6 18:57:48 dnsmasq-dhcp[2791]: DHCPACK(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb Gateway7C8CEB

It's too soon to tell if the device will be "kicked off" the network.

I am also having issues, so far this has happened twice, where I cannot log into the 86U via web GUI. The 86U just stops responding.
 
Thanks for the info. I'm a bit surprised that there seems to be duplicate entries in the log. Can you confirm how many instances of dnsmasq are running by posting the output of this command. It looks like the previous instance wasn't killed, or it restarted itself.
Code: 
ps w | grep dns
 
ColinTaylor said:
Thanks for the info. I'm a bit surprised that there seems to be duplicate entries in the log. Can you confirm how many instances of dnsmasq are running by posting the output of this command. It looks like the previous instance wasn't killed, or it restarted itself.
Code: 
ps w | grep dns
Click to expand...

I'm sorry for the late response. I regrettably fell asleep. Pretty much crashed.

So, the RIG is still connected since issuing that command. It has not disconnected or been "kicked off" the network.

The output of that command:

Code: 
2791 nobody    4908 S    dnsmasq --log-async
2792 agilis    4908 S    dnsmasq --log-async
2845 nobody    4908 S    dnsmasq --log-async --dhcp-broadcast
2846 agilis    4908 S    dnsmasq --log-async --dhcp-broadcast

Seems like there are 4 instances running!
 
Oh, OK. I think the way dnsmasq is invoked has changed.

Can you try killing old process(es) with:
Code: 
kill -9 2791 2792
and then verifying if again with
Code: 
ps w | grep dns

BTW Are you still running Merlin's firmware?
 
I ran:

Code: 
killall dnsmasq
dnsmasq --log-async --dhcp-broadcast
ps w | grep dns | grep -v grep

And this is returned:

Code: 
9780 nobody    4908 S    dnsmasq --log-async
 9781 agilis    4908 S    dnsmasq --log-async
 9973 nobody    4908 S    dnsmasq --log-async --dhcp-broadcast
 9974 agilis    4908 S    dnsmasq --log-async --dhcp-broadcast
 
ColinTaylor said:
Oh, OK. I think the way dnsmasq is invoked has changed.

Can you try killing old process(es) with:
Code: 
kill -9 2791 2792
and then verifying if again with
Code: 
ps w | grep dns

BTW Are you still running Merlin's firmware?
Click to expand...

I did what you said with the PID adjustment:

Code: 
 9973 nobody    4908 S    dnsmasq --log-async --dhcp-broadcast
 9974 agilis    4908 S    dnsmasq --log-async --dhcp-broadcast

Yes, I am running Asuswrt-Merlin 384.9 for RT-AC86U.
 
Code: 
ps w | grep dns | grep -v grep
9973 nobody    5040 S    dnsmasq --log-async --dhcp-broadcast
9974 agilis    4908 S    dnsmasq --log-async --dhcp-broadcast

The RIG is still connected and has not lost connection since executing the command:
Code: 
 dnsmasq --log-async --dhcp-broadcast
 
agilis said:
I did what you said with the PID adjustment:

Code: 
9973 nobody    4908 S    dnsmasq --log-async --dhcp-broadcast
9974 agilis    4908 S    dnsmasq --log-async --dhcp-broadcast

Yes, I am running Asuswrt-Merlin 384.9 for RT-AC86U.
Click to expand...
OK that looks better. Give it a couple of minutes and run the ps command again just to make sure those other two processes haven't magically reappeared. EDIT: OK you've just done that.

This might actually be mute anyway because in your post #46 we could see that the RIG was correctly getting its IP address from both versions of dnsmasq. Whereas before your problem was that it didn't get it for 50 minutes! So yet again this is inconsistent behaviour. :confused:

It's probably best to stick with Merlin's firmware for the moment because it shows you the DHCP activity which is what we're interested in.

I don't have discord.
 
ColinTaylor said:
OK that looks better. Give it a couple of minutes and run the ps command again just to make sure those other two processes haven't magically reappeared. EDIT: OK you've just done that.

This might actually be mute anyway because in your post #46 we could see that the RIG was correctly getting its IP address from both versions of dnsmasq. Whereas before your problem was that it didn't get it for 50 minutes! So yet again this is inconsistent behaviour. :confused:

It's probably best to stick with Merlin's firmware for the moment because it shows you the DHCP activity which is what we're interested in.

I don't have discord.
Click to expand...

Okay. I am planning on sticking with the Merlin software. I like the more comprehensive logging support.

Now, would you like me to restart the router once again and not do anything and see what happens? Because please keep in mind, this is the first time I connected the RIG to the network since it was brought home after being connected to my neighbor's network.

At this point I will only do what you want me to do while we are troubleshooting.

But again, RIG is still connected and has not lost its connection.
 
I'm not sure where we go from here. Your previous problem did not reoccur when you reconnected the RIG to the router.

I suppose the next thing to try is unplugging the RIG, waiting 2 minutes and then plugging it back in again. Then check the logs to make sure you see the DHCPREQUEST and DHCPACK messages.

If the above is successful repeat as many times as you want until you're confident it's working 100%.

The next step would be to reboot the router to lose the change you made and repeat the test above.
 
First attempt:
Code: 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPOFFER(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPREQUEST(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPACK(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb Gateway7C8CEB
Nov  6 20:55:20 dnsmasq-dhcp[9973]: DHCPSOLICIT(br0) 00:03:00:01:00:23:7d:82:43:57

Second attempt:
Code: 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPOFFER(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPREQUEST(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 20:53:59 dnsmasq-dhcp[9973]: DHCPACK(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb Gateway7C8CEB
Nov  6 20:55:20 dnsmasq-dhcp[9973]: DHCPSOLICIT(br0) 00:03:00:01:00:23:7d:82:43:57

Third attempt:
Code: 
Nov  6 21:41:56 dnsmasq-dhcp[9973]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb 
Nov  6 21:41:56 dnsmasq-dhcp[9973]: DHCPOFFER(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 21:41:56 dnsmasq-dhcp[9973]: DHCPREQUEST(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb 
Nov  6 21:41:56 dnsmasq-dhcp[9973]: DHCPACK(br0) 192.168.50.171 b8:2c:a0:7c:8c:eb Gateway7C8CEB
Nov  6 21:43:19 dnsmasq-dhcp[9973]: DHCPSOLICIT(br0) 00:03:00:01:00:23:7d:82:43:57

-
Received an IP each attempt.

-
Rebooted the router at 22:51

-
RIG hopped online immediately.

-
Code: 
ps -w | grep dns | grep -v grep
1265 nobody    4908 S    dnsmasq --log-async
1266 agilis    4908 S    dnsmasq --log-async

So far, the RIG has been connecting and staying connected.

Maybe 1 of 2 things happened:
  • The command you asked me to execute fixed it.
  • Connecting the device to a different router recalibrated something in the device (Even though the engineers/tech assured me that there is nothing saved to the device except the information for the thermostat link)
 
I am now making changes to the 86U, like changing the LAN IP to 192.168.1.1 and I watched the RIG lose the connection and then connect. It has never done that since I've been trouble shooting this.
 
I now have completed the following:
  • Set the LAN IP
  • Manually assigned all the IPs via MAC that I like having defined.
  • Configured the DNS that the router uses to my Raspberry PI that runs pi-hole.
  • Rebooted the router
Absolutely no issues so far.

Code: 
ps -w | grep dns | grep -v grep
1269 nobody    4908 S    dnsmasq --log-async
1270 agilis    4908 S    dnsmasq --log-async
 
You must log in or register to reply here.

Similar threads

N
Honeywell REDLINK gateway problem - some additional info
Replies
4
Views
3K
westcoastwillie23
W
I
IoT monitoring on RT-AC3200 asuswrt-merlin v384.13_10
Replies
2
Views
1K
itibi
I
J
Need help troubleshooting - problem started out of nowhere
Replies
10
Views
2K
JTnola
J
C
Need help: lightning damage?
2
Replies
21
Views
4K
Cloud200
C
T
Redirect internet traffic not working with openvpn
Replies
1
Views
14K
tossom
T

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 820 (members: 23, guests: 797)
Top