Recent content by tabormeister

Update: The issue with DoT was turning the built-in IoT network off. That's a bug w/ underlying Asus code.

I can't get half my Google Homes or my printer to work on this release of Merlin, will have to flash back to stock temporarily until that's fixed. Happy to troubleshoot or provide logs/diagnostic files if that would be helpful!

Looks like WiFi on BE98 isn't working after connecting an AX88U Pro AiMesh node running Merlin 388.7 - will try a full reset of everything and setting up fresh again.

Cool! I was wrong about DNS - I think it's a combo of me enabling IPv6 Native, then turning on DNS over TLS - I can't get DoT working w/ IPv6 on. Had to re-disable to get internet downstream of router again.

New bug: DoT (DNS over TLS) enabled set to Cloudflare servers for ipv4 and ipv6 kills traffic for devices on main VLAN. Turned it off and on again and now working fine.

All 3 done :) these are fresh off the press with a good clean config.

Update: If I go through the advanced settings, pick router, auto ip, etc. it'll let me actually finish the wizard and set up the router. Still a bit bugged as it only displays WiFi 7 and IoT networks, without option to split networks out.

Fresh setup flow for GT-BE98 Pro w/ Merlin has a couple bugs - 1. visual bug, snapshot of old RT-N66 style router 2. Functional bug - after selecting automatic IP, only 2.4ghz is shown, and the router freezes on this screen after apply.

So Asus took my XT8's back to review and see if there's an issue, I have a new set now (still hw 1.0) and am going to try hooking one up as a node. Updates to follow!

Going back and forth with asus, not promising

OK so interestingly I'm running one of the XT8 nodes on that beta firmware above, and one on 386 firmware and am not getting the cfg_server memleak anymore. Maybe try mismatching firmware versions to see if it does that nonsense?

Lol nope mine just started doing it again. Rolling back to 386 again.

I got a beta firmware from Asus engineers for xt8s while troubleshooting something different, try this https://www.asuswebstorage.com/navigate/a/#/s/CB7C3DDA15B740AD9F3D08A398A2A836Y

Flash back to 386. Solved it for me. 388 still pretty buggy in myriad ways (syncing guest network to aimesh nodes causes random ip dropouts on guest network from nodes as an example)

EXACT same behavior where killall cfg_server instantly returns webui to snappy as heck. What's up with that Asus? I'm also waiting on L2 support.