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

[agilis]

Great news @agilis. Good to know it's not a problem with your router after all.

I know!! What a relief. But such a waste of time and resources. Thank you for all your help and suggestions!! Wish you the best!!

 

[agilis]

Hello everyone,

Well... It's happening again and nothing changed on my network. Saturday night into Sunday the RIG lost connection. I power cycled the device. Came online. Great. But it's happening more and more frequently.

Now, I'm not seeing a flashing Amber or Green LED status light. I am seeing a Solid Amber LED status light, which according to the documentation, means this:

Solid Amber: Ethernet Connection Detected (cable connected and Gateway is retrieving the IP address)

The behavior I am experiencing:

1. Plug into power
2. All status LEDs green - Power, Internet, RedLink
3. Then it will lose connection (after an indeterminate time) and the Internet LED will change to solid amber.

Update: Change from Green to Solid Amber took about 9 minutes.

I am doing my absolute best to troubleshoot this again and I am growing very tired of what it could be. Things I have tried:

• DHCP Lease time adjusted to 7 days
• Restarted router
• Static IP via Mac Addr
• DMZd IP for RIG (192.168.1.50)
• Switched ethernet ports RIG is connected to
• Moved device to the AiMesh node
• Allowed ICMP Ping

I don't understand why this is happening and I don't know how to troubleshoot it further. This device cannot have gone bad. The odds, my luck, would have to be so low and so bad.

Thanks in advanced for anyone willing to help.

 

[agilis]

Hello everyone,

So after talking to the same tech yesterday for about 2 hours, we have still gotten no where. The behavior I described above is the same behavior that occurred while I was the phone with him.

So he asked me to send him screen shots of my router's configuration so that he can forward them to the engineering department and have them recreate the issue.

This afternoon the tech suggested I try to connect the RIG directly to the back of the cable modem, completely bypassing the router.

THIS WORKED

It maintained a stable connection for 1 hour and 10 minutes.

I then reconnected the router to the cable modem and the RIG to the router.

THIS DID NOT WORK

My router and its configuration definitely seems like the cause.

 

[agilis]

Additional Screen shots attached.

 

[OzarkEdge]

I wonder what happened to the findings identified in this post:

[URL ]https://www.snbforums.com/threads/d...net-gateway-happening-again.67157/post-627342[/URL]

My gut feeling is that it should just work, assuming any special purchase/setup requirements have been satisfied by you. So, Honeywell is not off the hook, imo.

The DHCP default gateway IP address can be left blank. The router's LAN IP address will be used.

You could try setting a public DNS address like QUAD9 9.9.9.9 and 149.112.112.112 instead of using your ISP DNS.

Have you tried using your own Ethernet cable instead of the one that comes with the Honeywell unit?

Beware assuming what is not the problem... this may cause you to overlook the problem.

OE

 

[ColinTaylor]

This is something of a desperate suggestion, but can you try swapping around your two Asus'? So the RT-AC88U becomes the main router and you're connecting directly to that.

 

[agilis]

Thank you very much for your response. I also really appreciate taking the time to look over the pictures and your suggestions. I'll try to answer all your questions.

So the original post is from me. I never thought to connect the RIG directly to the cable modem, until this afternoon. Once I did that, I was able to narrow down the issue to being the router or its configuration.

I started this thread to ask for wide-spread help regarding, I guess break through, on my on-going issue.

1. I removed the default gateway IP from the textfield.
2. For the DNS, I connected the RIG directly to the cable modem and it worked correctly.
3. I have tried swapping ethernet cables.

I agree with you that this device should just work. And out of all the devices I have connected, this is the only device failing to stay connected to my network.

- Rick

 

[agilis]

This is something of a desperate suggestion, but can you try swapping around your two Asus'? So the RT-AC88U becomes the main router and you're connecting directly to that.

Hello Colin, you been so patient and have helped me a lot regarding this on-going issue.

I had the RT-AC88U as my router once but someone on here suggested I make the RT-AC86U the router because it has a faster CPU. In order for me to switch, I'd have to remove it from being an AiMesh node reconfiguring the entire system once again however I'd like to Export/Import the configuration so I don't have to re-do it a second time.

Thank you,

- Rick

 

[ColinTaylor]

Yes the RT-AC86U would normally be the better choice for the primary router. Like I said, it was a desperate suggestion.

Regarding your "Export/Import"; that's fine if you're only planning to backup your current setup so that you can go back to it in the future (if the swap around doesn't help). However, don't try to import a backup config from one router to a different router. That's not a supported procedure.

 

[agilis]

Yes, that would be my plan. Back up the configuration so it can be later imported.

If I attempt this it's going to take me offline for a bit. My mind is all over the place so I've got to plan how to do this quickly and efficiently as possible.

 

[ColinTaylor]

Ideally you would want the problem to manifest itself straight away, rather than after hours/days.

If that were the case then it could be something that could be tested very quickly with a temporary single-router setup. However, if this is going to be semi-permanent then careful planning will indeed be required.

 

[agilis]

I switched out the routers and I am now using the RT-AC88U as the router and the 86U has been set aside.

The firmware on the 88U is the latest and current. Nothing has been configured from the default except the LAN IP and Wireless SSID and password.

As of now:

• RIG is connected
• My main ethernet switch connected
• Upstairs device connected

So far the hold on the IP address by the RIG, the internet connection, etc. has been stable for 30 minutes.

I believe the issue is resolved when connected to the 88U.

Now, where do I go from here? I've restored the 86U but not since I started having the issue again shortly after the daylight savings time change.

 

[ColinTaylor]

So far the hold on the IP address by the RIG, the internet connection, etc. has been stable for 30 minutes.

I believe the issue is resolved when connected to the 88U.

Isn't that a bit too early to say? You thought it was fixed on Oct 23 but then it failed again 8 or 9 days later (if I understand your previous posts).

Now, where do I go from here? I've restored the 86U but not since I started having the issue again shortly after the daylight savings time change.

I'm not sure what you mean by "I've restored the 86U". Do you mean you haven't done a factory reset on the 86U since...?

 

[agilis]

Isn't that a bit too early to say? You thought it was fixed on Oct 23 but then it failed again 8 or 9 days later (if I understand your previous posts).

So with my testing, the RIG's internet status light would transition from solid green to amber within 15 minutes. It's been solid green for an hour. Now you're right... this was working correctly on October 23rd. Then all of a sudden it failed and like I said, it started shortly after the time switch on Sunday morning.

So it might be too early but the fact it has not transitioned from amber for about an hour now, makes me thing it won't.

I'm not sure what you mean by "I've restored the 86U". Do you mean you haven't done a factory reset on the 86U since...?

Meaning that I performed a factory reset on the 86U prior to the 23rd but I have not done one since.

 

[ColinTaylor]

Well if it holds up OK you could leave the 88U as it is and use the 86U as the node/AP. Is that feasible? The two devices are almost identical in terms of WiFi. The only real differnce is the hardware encryption on the 86U which is useful if you're using its VPN, and the extra LAN ports on the 88U. If you don't need the VPN performance or the switch ports you may as well leave the 88U in place.

 

[agilis]

Also since swapping to the 88U I've noticed that the 2.4GHZ band is no longer showing up, and this is after a restart. Uggh. My luck is just so bad

 

[agilis]

Well if it holds up OK you could leave the 88U as it is and use the 86U as the node/AP. Is that feasible? The two devices are almost identical in terms of WiFi. The only real differnce is the hardware encryption on the 86U which is useful if you're using its VPN, and the extra LAN ports on the 88U. If you don't need the VPN performance or the switch ports you may as well leave the 88U in place.

It's definitely an option but kind of would like to resolve the issue with the 86U. I'm going to end up performing a factory reset on the 86U soon.

 

[agilis]

The 88U is being reset back to factory defaults in hope to get the 2.4Ghz band working again. I will be looking into another option for wireless.

Also, I have factory reset the 86U once again. It is back in place as a router with the RIG connected and the stability of the internet connection for that device has been stable since.

So this anomaly that I was seeing with this device *may* have been solved with a factory reset.

 

[agilis]

Hello so I've been beyond busy trying to solve this issue and I'm exhausted & frustrated.

Here is what I've tried since:

- Swapped 86U with 88U: Successful
Note: Discovered 88U's 2.4Ghz band does not work.

- Factory reset 86U while removed from network with Laptop.

1. Preconfigured 86U first.
2. Swapped 88U with 86U after

Successful? (Waited 30-40 minutes)

- Made modifications to configuration:

• LAN IP
• LAN: DHCP Server: Manual Assignments
• WAN: DNS

Unsuccessful

- Cleared WAN DNS: Unsuccessful

- Removed all DHCP server manual assignments : Unsuccessful

- Changed LAN IP: Unsuccessful

Restored to Factory Defaults: Unsuccessful

- Downgraded firmware and Factory Reset:
Version 3.0.0.4.384.82072
2020/08/17

Unsuccessful

- Downgraded firmware and Factory Reset:
Version 3.0.0.4.384.81992
2020/07/09

Unsuccessful

- Downgraded firmware and Factory Reset:
Version 3.0.0.4.384.81930
2020/06/17

Unsuccessful

- Downgraded firmware and Factory Reset:
Version 3.0.0.4.384.45713
2019/04/18

Results not available: Router for some reason after initialization was using default SSIDs for both 2.4G and 5.0G bands. When I went to update the SSID to force a change, the router reset and updated itself to the latest firmware.

- Factory reset 86U while removed from network with Laptop.

1. Preconfigured 86U first.
2. Installed it back onto the network

Unsuccessful

- Installed ASUS Merlin 384.19: Unsuccessful

Merlin is spamming to the log the following over, and over, continuously:

Nov 6 11:47:17 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:17 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:26 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:26 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:26 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:26 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:28 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:28 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:35 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:35 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:42 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:42 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:47:53 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:47:53 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb

b8:2c:a0:7c:8c:eb is the MAC address of the RIG.

After about 50 minutes, this happened:

Nov 6 11:50:30 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 11:50:30 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:50:31 dnsmasq-dhcp[1265]: DHCPREQUEST(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 11:50:31 dnsmasq-dhcp[1265]: DHCPACK(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb Gateway7C8CEB

In about 9 minutes...

Nov 6 11:59:57 dnsmasq-dhcp[1265]: DHCPRELEASE(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 12:00:01 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 12:00:01 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 12:00:01 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 12:00:01 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 12:00:04 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 12:00:04 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb
Nov 6 12:00:09 dnsmasq-dhcp[1265]: DHCPDISCOVER(br0) b8:2c:a0:7c:8c:eb
Nov 6 12:00:09 dnsmasq-dhcp[1265]: DHCPOFFER(br0) 192.168.50.172 b8:2c:a0:7c:8c:eb

And this cycle continues.

I'm taking the RIG to my neighbor's house which has the exact same router to try it on their network.

 

[agilis]

Device has been connected to my neighbor's router, RT-AC86U for over 2 hours without any issues.