Router.asus.com doesn't resolve

ASUS AX-86U running merlin 3004.388.11

adam one version 4.16.1-1 | RT-AX86U_EPA@388.11

I can open my box via https://192.168.50.1:8080/, but https://router.asus.com:8080 doesn’t. Ping ‘router.asus.com’ ‘Ping request could not find host router.asus.com’

I’m sure it’s an easy fix, but it eludes me.

Hi @Mark_Nadig , thanks for reporting this.

Can you please check the contents of /etc/hosts on that ASUS router?

Hi @Bill , thank you for the reply. cat /etc/hosts indicates the file is empty.

Thanks Mark.

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.

I powered off the router, gave it 15s and then back on, and it’s still empty

admin@RT-AX86U-6960:/tmp/etc# ls -la hosts
-rw-rw-rw-    1 admin    root             0 Sep 22 09:18 hosts

thanks for your help.

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.

Hope that helps.

Hi Bill, thanks again.

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 may have to the Asus Firmware util to load that unless you think there’s an easy way to drop that memory. It’s only running AdamOne.

Hi Mark.

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?

I appreciate all your help.

Best,

Mark

@Bill , seeing this in the server log:

Oct 2 11:25:14 kernel: potentially unexpected fatal signal 11.
Oct 2 11:25:14 kernel: CPU: 2 PID: 11620 Comm: anmuscle Tainted: P O 4.1.52 #2
Oct 2 11:25:14 kernel: Hardware name: Broadcom-v8A (DT)
Oct 2 11:25:14 kernel: task: ffffffc02be09480 ti: ffffffc029b6c000 task.ti: ffffffc029b6c000
Oct 2 11:25:14 kernel: PC is at 0x109d8c
Oct 2 11:25:14 kernel: LR is at 0x11700c
Oct 2 11:25:14 kernel: pc : [<0000000000109d8c>] lr : [<000000000011700c>] pstate: 60070010
Oct 2 11:25:15 kernel: sp : 00000000ff95de90
Oct 2 11:25:15 kernel: x12: 0000000000dff5a4
Oct 2 11:25:15 kernel: x11: 00000000ff95e220 x10: 0000000000000000
Oct 2 11:25:15 kernel: x9 : 0000000001d5b180 x8 : 0000000001d5b1c0
Oct 2 11:25:15 kernel: x7 : 0000000001d5b1c0 x6 : 0000000000000000
Oct 2 11:25:15 kernel: x5 : 0000000000dff5a4 x4 : 0000000000dff5b0
Oct 2 11:25:15 kernel: x3 : 0000000000000000 x2 : 0000000001c55370
Oct 2 11:25:15 kernel: x1 : 0000000001c554ec x0 : 0000000000000000

Hi Mark,

Thanks for providing those details.

Quick question: Is adam:ONE® functioning properly otherwise?

I just wanted to reaffirm that the primary need is still getting router.asus.com to resolve correctly. Let me know.

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)?

Thank you.
Mark

According to Stage 3, Step 6 of the adam:ONE installation guide for Asus routers, you can retrieve your Box ID via SSH using the following command:

grep box-id /jffs/addons/adamone/muscle.conf | cut -d= -f2

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.

Hi,

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.

But…

still can’t access https://router.asus.com:8080 :confused: Before re-installing adamone I was accessing asusrouter.com for the router UI. https://192.168.50.1:8080 works w/ cert warning. Crazy :slight_smile: Is there anything you’d suggest so router.asus.com resolves? thank you again for all your help.

Mark

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?

Best,
Mark

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.

Mark