Recent content by Matthew Patrick

The new Beta fixes the issue where if my wan0 went down. After it moved to wan1. It won't ever go back to wan0 when it's up because the script will still see it as having 100% packet loss. Usually only a script restart fixes this but this new Beta fixed it completely

Nice! If it does it per band without interrupting the other band. It should be good too!

Yep but I think that will restart the whole wifi interface. So both 2.4 and 5ghz. If radio off and on 0 works fine. It should be better since it will only do the 2.4ghz which means devices connected to the 5ghz band will be uninterrupted. Oh and If there are clients on the 2.4ghz that supports...

Mine doesn't do that but if it does that again. If you can on Merlin go to ssh and try. "radio off 0" . Wait a few sec. Then "radio on 0". Does that fix the 2.4ghz? If yes you can just create a cronjob to do it automatically. It should only restart the 2.4ghz. That way you don't have to reboot...

I don't use mesh. But, Asus mesh system should act like an AP instead of a router so the IP should be the same. This means if your main router is hosting the SMB server. It should still be fine when you're connected to the other mesh. For number 2 I don't know for sure. I do know that it...

If your USB is being hosted at your router using SMB etc. Then Asus mesh should work fine. I don't know if you need the USB to be plugged in to the main router though. Never tried using Asus mesh before.

Just make sure to check the command when you run it so it only removes the asd folder! :P

I saw that on some it's a different file (different name) but yeah safest way is probably to remove the whole asd folder since rebooting will redownload everything anyways :)

So i assume you only need the commands right? Then you should be able to do this rm -rf /jffs/asd After that you can just exit out and click reboot on WebGUI. It should reboot and everything should be fine. Monitor it and if your problem was because of the asd bug, this should fix it AFAIK...

Just do this and if it's the asd bug that you're currently experiencing. It will be fixed after removing /jffs/asd folder and rebooting.

Sadly it didn't work for my family's Asus router. I did the remove asd folder and reboot to fix it.

You can just ssh it. Ssh to router, then remove everything on asd folder on /jffs . Reboot. It should rebuild everything at boot and it should be the fixed version. No it won't mess up future asd updates since it is basically the same thing as when you reset the router or format the jffs. Edit...

I think AIProtection etc uses the Trend Micro Signature files right? They have a different folder and the update can be triggered via WebGUI. Whereas asd one is automatic it seems like. Is there a way to force it to update the files? Probably not?

I see. So 386.10 and 11 should be fine . Thank you for the response!

From what I saw. It's already fixed (?). Need others to chime in. I think it's just that some still have the problematic file. I think the newer one that it pulls after you removed the problematic file is fixed.