Recent content by Gtothe

I have the same issue... I ended up going all the way back to 384.13 I hope this gets resolved

I rather not have 30+ seconds of downtime every 30 minutes. I'll wait for a stable 386 release. I checked the 386.41994 thread and it seems like there's quite a few bugs. Takes me a whole day to get all my routers set up correctly and I rather not test a beta non-merlin build just to see if it...

Of course its not a Merlin issue. Never meant to imply that. I was mainly trying to help people with AIMesh stability issues and see if anyone has experienced similar issues

I have already tried that on a few different firmware versions. It only enables SSH on the main router

Yes. I went from 384.17 where I had issues to 386.2_4 and it was no better. Also, I can't find a way to enable SSH on the aimesh node so I can check the logs to see what is going on. Aimesh is pretty half assed. It's been like 2 years and they can't get it right on a 7 year old router.

Around 384.17 or 18 the password storage mechanism changed. That means you need to reset the router in order to log in. Also nodes have to be on the same firmare or they won't connect. You can't have the router on a new firmware and the node on a substantial older firmware or it will not work...

I kinda want to stay with Merlin firmware since it has a few features I need and I don't see a Merlin software using GPL 386.41994. Edit: I see that 386.41994 is a beta so I guess I will have to wait a while. Also upgrading and downgrading is a hassle since I have to reset everything on all my...

I've tried a few firmwares and the only ones that work without random dropouts is fw 384.13. I am using 2 "RT-AC68U"s The only problem I have now is that let's encrypt is not working anymore (ACME v1). I wish there was an easy way to back port Let's Encrypt ACME v2 from 384.13_2 which is a...