GT‑AX6000: Mastiff Crash Loop Every 30 Seconds After Full NVRAM + Factory Reset

[SwoopdySwoop]

Hi all,

I’m running into a persistent Mastiff crash loop on my GT‑AX6000 that continues even after a full NVRAM wipe and factory reset. I’m hoping someone can help me identify what’s causing this.

Symptoms

Mastiff restarts every ~30 seconds, continuously, with watchdog messages like:

rc_service: watchdog ... notify_rc stop_aae
rc_service: watchdog ... notify_rc start_mastiff
Mastiff: init

This repeats indefinitely.


I also see roamast events in between the crashes:

roamast: determine candidate node [...]
roamast: Roam a client [...], status [0]

What I’ve Already Done

• Full NVRAM erase (via SSH: mtd-erase2 nvram)
• Full factory reset from GUI
• Rebuilt configuration manually (no restore file)
• Reset all AiMesh nodes
• Ensured firmware versions match across devices

Despite this, Mastiff still enters a crash loop immediately after boot.


Additional Notes

• Two node MACs appear in the logs even after resets:
  • A2:9C:25:57:78:45
  • 7C:10:C9:05:1D:7C
• I’m trying to determine whether this is:

• A ghost AiMesh node
• A firmware bug in the roaming/AAE stack
• A corrupted roaming table that survives resets
• Or a hardware issue with the radio

Questions

1. Has anyone seen Mastiff continue to crash after a full NVRAM wipe?
2. Could ghost AiMesh entries survive a reset, and if so, how do I purge them?
3. Is there a known firmware build where Mastiff/AAE is unstable on the GT‑AX6000?
4. Any recommended steps to isolate whether this is firmware vs hardware?

Any insight would be appreciated — this one has me stumped.

Thanks!

 

[ColinTaylor]

Frequently reported problem. Set:

Administration - Tweaks > Disable Asusnat tunnel = Yes.

 

[SwoopdySwoop]

Love you. TY!