Likely the SSH key has changed.
Did you try deleting the old key?
www.snbforums.com
Did you try Asus original firmware on the RT-AX58U? IMO since its operating as an AI-Mesh node it really doesn't need Merlins firmware.I was wrong! Dirty upgrade lives on! Now testing with RT-AX88U (main), RT-AX86U, and RT-AX58U AiMesh nodes.
[Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)
My Configuration: AiMesh Router: AX88U 386.1_alpha4-gd4b7146753 + 2 x AiMesh Nodes: AC86U 386.1_alpha4-gd4b7146753 Backhaul (Priority:"Auto", Type:"Wired"), Cisco SG100D 8-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre My Test Exercise with Alpha4: Full Factory Reset of AiMesh...
Just a quick update on this (please see the details in the link above.
I was able to add an RT-AX86U as an AiMesh node even though the RT-AX58U could not be connected, even with all the things I tried as outlined in the link above. The RT-AX86U as a node is superior, btw (vs. the RT-AX58U when it worked on Alpha 3 and now on Alpha 4).
Without needing to stop, disable, or otherwise hamper any scripts (nor physically removing the USB drive either), how I got the 'AX58U to connect was by connecting it to the main router via it's WAN port.
The testing continues but just wanted to report the progress so far.
Lesson learned: AiMesh should connect wirelessly, but it doesn't hurt to test wired mode either.
ya-malware-block.sh script should be modified to recognise/allow "v7" whilst suppressing the "Warning:" message textcase $(ipset -v | grep -o "v[4,6]") in
v6) MATCH_SET='--match-set'; CREATE='n'; DESTROY='destroy'; RESTORE='restore'; ADD='add'; SWAP='swap'; IPHASH='hash:ip'; NETHASH='hash:net'; ESL=7
lsmod | grep -q "xt_set" || for module in ip_set ip_set_hash_net ip_set_hash_ip xt_set; do modprobe $module; done;;
v4) MATCH_SET='--set'; CREATE='-N'; DESTROY='--destroy'; RESTORE='--restore'; ADD='-A'; SWAP='--swap'; IPHASH='iphash'; NETHASH='nethash'; ESL=6
lsmod | grep -q "ipt_set" || for module in ip_set ip_set_nethash ip_set_iphash ipt_set; do modprobe $module; done;;
*) logger -t Firewall "$0: Unknown ipset version. Exiting." && exit 1;;
esaccase $(ipset -v 2> /dev/null | grep -io "v[4-9]") in
v6|v7) MATCH_SET='--match-set'; CREATE='n'; DESTROY='destroy'; RESTORE='restore'; ADD='add'; SWAP='swap'; IPHASH='hash:ip'; NETHASH='hash:net'; ESL=7
lsmod | grep -q "xt_set" || for module in ip_set ip_set_hash_net ip_set_hash_ip xt_set; do modprobe $module; done;;
v4) MATCH_SET='--set'; CREATE='-N'; DESTROY='--destroy'; RESTORE='--restore'; ADD='-A'; SWAP='--swap'; IPHASH='iphash'; NETHASH='nethash'; ESL=6
lsmod | grep -q "ipt_set" || for module in ip_set ip_set_nethash ip_set_iphash ipt_set; do modprobe $module; done;;
*) logger -t Firewall "$0: Unknown ipset version. Exiting." && exit 1;;
esacI had an issue where the WAN went down and went into my MTU setting and it was blank. Once I set it to 1500, the wan worked and everything was fine.
If you do this I'd suggest skipping the
&& reboot to make sure there are no error messages after the flash. The reboot may occur before you have the time to observe any messages (the flash process itself is silent if successful IIRC).I suspect entware/spdmerlin or scmerlin casing issues.
