Recent content by ghalidrim

Been seeing the same, or similar issues with AX68U as a mesh node (look back in this thread for other examples). So far, there's not much that can be done as it's all closed source. I'm hoping the latest official release includes fixes due to the patch notes, and that those will be rolled in.

Upgraded all my devices to beta 2 today. Did not see a direct repeat of the issue I previously had. My two AX88U nodes continue to be fine and my AX68U node stayed connected to the AIMesh. It is showing an error in the UI (attached) but devices have connected to it and are working fine as near...

I have two AX88Us, one as router one as node, those joined fine. My AX68U will not join no matter what on 388.1_beta. Downgraded the AX68U to 386.7_2 and it joined immediately and with no issue. So something in the new 388 release is keeping AX68Us from joining, and I'm willing to help figure...

Something is keeping AX68's from joining meshes though, there are several folks in here reporting it on only that model. Any idea from the Asus folks on what might be happening there?

Dug into why my AX68U can't join the AIMesh a bit more and I'm seeing the same log entries for every attempt to join it, but these don't seem catastrophic: Nov 8 07:56:57 home kernel: device br0 entered promiscuous mode Nov 8 07:56:58 home lld2d[1241]: get_icon_image: reading iconfile...

Having the same problem on a AX68U, my AX88Us both upgraded and running mesh router and node fine, but my AX68U refuses to be set back up as a mesh node. I've reset it and factory reset it and it always fails at the 50% level both wired and on wireless.

I'm having the same problem as above. I have to type the whole FQDN into the DDNS page for Let's Encrypt to succeed, but then DDNS does not properly update the record at Namecheap. Name cheap is expecting the host name only, as the domain is used to login.