Rebooted the router and the Chromecast several times. Didn't help.@Geraner what, if any, troubleshooting steps have you taken so far?
Moving furth and back Beta.4 to Beta5, and 386.1 release and now the ChromeCast is working normally also with 386.1 release. - Strange, but now it works.Rebooted the router and the Chromecast several times. Didn't help.
Moved now back to 386.1_beta4. Restarting the Chromecast, and everything is working again.
Will continue testing more with beta5+ 386.1 release during the day and report back later.
Make sure you religiously copy the OVPN file to the correct folder \program files\OpenVPN\Config if using 11.20.00 or import profile when using OVPN Connect. Make sure you dont have extraneous OVPN files from older configs lying around your directory structure or import the correct profile when using Openvpn Connect.
I also have 2.4ghz clients (Shelly) dropping off with 386 but it could well be a bug with the latest Shelly FW.Yeah it's been 14 hours or so and nothing has dropped on my 2.4ghz . Seems like it is 386 issue. Idk what tho. So weird...
No -= i do not have the guest network setup at all. They are all 2.4 units that fail.Were the offline clients using Guest network 1?
NM, found the answer in the changelog link https://www.asuswrt-merlin.net/changelogQuestion regarding upgrade to 386.1 from the latest Beta fw for the ac86u:
ASUS RT-AC86U Firmware version 9.0.0.4.386.41994 (Beta Version)
Security Fixed:
Fixed CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686
386.1 notes state: Merged with GPL 386_41700
Clearly the 41994 is newer, but are the CVE's already fixed in 386.1. Eric is ahead of the game in many ways, are these CVE's patches/unpatched or not relevant anyway? Would you be going backwards if you upgrade from .41994 to 386.1? Going backwards, meaning strictly from fw point of view, not features, etc.
Yeah it's just like when you do a clean install. Just install the 384.19, after it rebooted. Make sure it is now 384.19 if it is. I recommend to just go straight to wps reset. Since it apparently wipes the jffs too ... I do not reset since i already have a working 384.19 backup before going to 386 . So I just went to 384.19 and then restored both jffs and the backed up configuration..
The only thing I hate about 384.19 atleast in my AC86U is that it seems like there's a memory leak. Seems like it's from trend micro stuff but idk. I can see it go up in ram usage per hour and yeah I can see it pushing to swap usage after a day or two. And I don't use much addons. It's fixed on 386 though since I've run it for 2 days and the ram usage is consistent there. But yeah let me know if you experienced 2.4ghz problems as well. So far 4 and a half hour on 384.19 and 2.4ghz is still going strong. Will check it regularly to see if it happens here or not. I'd assume not
The thing is, it's dropping those things on guest network 2 or 3 and when it's happening, my 2.4ghz is basically broken. Can't join and the clients connected to it can't access anything. It can't even ping the router.. until it's done doing it's thing..I also have 2.4ghz clients (Shelly) dropping off with 386 but it could well be a bug with the latest Shelly FW.
Go to the System log tab. There find the Wireless log subtab. There you can monitor it if it disconnects or not..Updated, I will now see how 2.4ghz is over the next few days, I currently have left a few things disabled that I normally run, such as Ai protection and a guest network, I will gradually introduce them.
Is there anywhere on the router that I can view, to be able to tell if 2.4ghz has dropped, as I'm not always using the devices that require 2.4ghz so might not notice.
Also have set the 2.4ghz to 20hz and set a channel, 6 in my case.
I have also gone into the 2.4ghz wireless professional tab and disabled all the beamforming check boxes. These are things that have been advised to do on these very forums for stable wifi.
The thing is, it's dropping those things on guest network 2 or 3 and when it's happening, my 2.4ghz is basically broken. Can't join and the clients connected to it can't access anything. It can't even ping the router.. until it's done doing it's thing..
Seems fine on 348.19 tho. Monitored it for 24 hours. Doesn't drop any of my clients on 2.4ghz
Not exactly a screenshot, but very useful:Someone mentioned a screenshot you could copy information from. I think it was @L&LD, can you give me some more information about it please sir?
Ah I see. I'm still puzzled on why it's happening on my AC86U when I'm on 386 ... And just checked again and it's still fine. Almost 24 hours without any dc etc. Weird huhI went back to 386.1 beta 2. No problems at all. It runs great. Both radios working fine. Its snappy when I open a browser. Kids not complaining. I'm thinking of at least moving to beta 5 but I don't want to ruin a good thing. I would go to 384.19 but I love the Aimesh 2.0 interface.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!