I’m wondering if it’s /tmp/etc/hosts then (when SSH’d into the router)? What I was looking for was to see if router.asus.com was one of the hostnames listed there. The list of hostnames should be generated dynamically by the router firmware on boot up.
It’s odd that the router/firmware is not generating the hostnames.
In the as-is state, two options:
a) create an authoritative rule for router.asus.com in the dashboard pointing to the router IP (preferred) or,
b) create an entry in the hosts file (not sure whether that survives a reboot).
However, to solve the actual root issue, what I’d likely try first if you have not already, would be to ensure your model of ASUS router is on the latest Merlin firmware.
I downloaded latest RT-AX86U_3004_388.12_2 (currently .11) but having difficulty installing as it stops after upload with “firmware upgrade unsuccessful. This may result from incorrect image or error transmission.”, I confirmed the sha is correct. I suspect free memory.
I’m not sure how to drop the RAM usage. I just checked my home ASUS RT-AX56U and it’s less than 60% running intense logging (although I’m not sure if that effects RAM), so 89% does seem high? If you want, although I’ve never run across anyone needing to do this, you could try uninstalling adam:ONE (backup first if custom settings), disconnect/removed the USB thumb drive, reboot the router, and try again?
Bill, thanks again for your help. With some help from Gemini, I identified /tmp was filled up with admin@RT-AX86U-6960:/tmp/home/root# du -k /tmp/* | sort -rn | head -n 10 27604 /tmp/core-anmuscle-0-3840-11-1790961638-0 27512 /tmp/core-anmuscle-0-3331-11-1790961637-0 27512 /tmp/core-anmuscle-0-3317-11-1790961636-0 27512 /tmp/core-anmuscle-0-3313-11-1790961635-0 27512 /tmp/core-anmuscle-0-3308-11-1790961634-0 27512 /tmp/core-anmuscle-0-3304-11-1790961632-0 27512 /tmp/core-anmuscle-0-3300-11-1790961631-0 27512 /tmp/core-anmuscle-0-3295-11-1790961630-0 27512 /tmp/core-anmuscle-0-3291-11-1790961629-0 27512 /tmp/core-anmuscle-0-3285-11-1790961628-0
I cleared those out and my memory freed up enough to update the firmware. It’s 3004.388.12 now. However, after applying the update, I see those coredumps are back. Can you help identify the root cause?
Hi @Bill , thank you for checking in. The router was behaving poorly, so I nuked: uninstalled adam one, did a 30-30-30, reinstalled latest Merlin. 3004.388.12_2. It is running stably. I’m ready to re-install Adam One. Since I nuked it, I imagine I lost a lot of my settings, which isn’t a big deal. I’ve got ~ 24 devices. 20 of those are on my guest network as they are my IoT devices which I plan on setting up in a single group for “allow only the good”. My 4 other devices (work & home pc and two iphones) are on my primary network and will likely set up with “block the bad”. Any recommendations apart from that?
Then other question, when I re-install, I think by default it will be considered a new box on my account. Is that fine, or should I try to transfer to boxid (which I’m assuming I see on the billing page)?
Because you are using the same physical router, your Box ID will remain unchanged. However, since the device was completely wiped, you will need to reauthorize it in your dashboard after reinstallation. You can follow the steps outlined in our Reauthorize Router after Doing a Factory Reset guide to complete this process.
Recommendations for Policy Shaping:
Allowlist Approach (Recommended): Our ideal best practice is to operate from an “Allow only the Good” (Allow List Type ZeroTrust) policy model.
Blocklist Approach: If you choose to operate from a “Block the Bad” (Block List Type) policy model, we strongly advise utilizing DNSharmony®. This feature allows several upstream DNS resolvers to work in unison, ensuring that if any single resolver flags a domain for a bad reputation, the domain is immediately blocked.
I did re-install AdamOne and re-authorized in the Dashboard. Everything seems to be back up and running just fine. Memory usage seems stable and system log is relatively quiet. All good.
I see this is where we were at before I went down the rabbit hole of getting the latest Merlin on. So, sounds option A is preferred. Can you point me to where that would be in the dashboard?
Is there anything else I can help do to identify the actual root issue before working around?
Hi @Bill , I’ve migrated my account from the legacy account to latest DNSHarmony and all devices are on the Basic Filtering policy. Can you show me how to create the authoritative rule for router.asus.com ? thank you.