After two days it seems the problem has been solved. No network degradation in the morning and the one SSID is working great. Thanks a lot for the help!
Good tip about the guest network, Jong. I usually enable it when we throw a party and I'd prefer to enable it on the AP since it's where...
I typically test the WiFi with my Nexus 5 or Nvidia Shield Tablet. It could have been a bug in an older firmware, or I could have set it up wrong. I'm totally willing to admit that.
Right now I have the AP set back to 192.168.1.2 and the Core Router set to 192.168.1.1, mostly so I can access...
I typically do all of this except for the SSIDs. No matter what I do, I see an SSID in my list for each router, even when the name is identical. Ideally I'd like to just have the one SSID for my whole network. However if they're both going to broadcast a separate SSID, I've been naming them...
The problem still persists this morning, after setting the AP to 192.168.2.1. I'd post the logs but it looks the same as above, a flood of packets hitting my core router, making it impossible for other traffic to get anywhere.
I'm guessing this is the fix you are referring to. I'll apply the...
Destination Host Unreachable.
I haven't tried setting the AP to 192.168.2.1 yet but I'm working on that now. I'll update my results in the morning. Really appreciate the extra set of eyes on this issue.
For the past 8 months I've been chasing different issues on and off. Almost every time I have an issue, flashing the latest Merlin firmware and resetting to factory defaults solves the issue for many months. That is, however, till this recent incident.
I own two ASUS RT-AC87U units. One is my...