Grisu
Part of the Furniture
Easy done on parent-mesh, just in mesh-node list click on ' - ' will delete it from mesh list. Node will reboot and start with intitialize page.I don't see how to un aimesh it anywhere in the menu.
Easy done on parent-mesh, just in mesh-node list click on ' - ' will delete it from mesh list. Node will reboot and start with intitialize page.I don't see how to un aimesh it anywhere in the menu.
My router doesn’t even update those pages anymore either, although it blocks me when visiting malicious test pages.The alerts aren't really useful. They have no relevant information. You are better looking at the new tabs included in the new code base.
http://192.168.1.1/AiProtection_MaliciousSitesBlocking.asp
http://192.168.1.1/AiProtection_IntrusionPreventionSystem.asp
http://192.168.1.1/AiProtection_InfectedDevicePreventBlock.asp
Just an update in case it helps anyone else. My ac88 wireless has been pretty solid since trying out stock 3.0.0.4.384_21045 . So hopefully once the GPL for this gets released we can get an updated version of merlin that has the same fixes. I don't see any of the dhcp loops in my logs either. I am still seeing the error "received packet on eth1 with own address as source address" not sure what is causing that.
I also am trying aimesh and added an aimesh node in addition to the two repeaters. It appears to be working pretty solid, but its very annoying not being able to separate the SSID or get logs directly from the device like repeater mode. Not exactly a lot of options to configure either. I can't even tell what ssid the clients are connected to or at what speed, just that they are connected to the aimesh node. Can't even get into the menu, it redirects back to the core aimesh router. You can at least ssh into it should you decide you need to a full wipe though. I don't see how to un aimesh it anywhere in the menu.
no DSL type modem-routers are supported by Merlin!Hi all
Im a newbie here but I have a very quick question is the ASUS DSL-AC88U supported I cant see the DSL mentioned on the supported router section.
Thanks
Hi all
Thought I'd share my frustrating experience attempting to upgrade to 384.5, coming from 384.4_2.
Lacking any expert technological knowledge, I have always relied heavily on this community for previous upgrades, particularly as regards reboots/resets/flushes etc.
To the point: I can't manage to get the internet connected (I appreciate the issue may reside with my ISP).
If anyone can point to flaws in my process, I'd love to read you...
I proceeded as follows:
-Since John's great back up tool (https://github.com/RMerl/asuswrt-merlin/wiki/NVRAM-Save-Restore-Utility) can no longer be used for the 384 mod, I manually backed up as much as I could (DCHP static list, jffs, etc) and screenshot the rest of the settings.
-Downloaded the fw (at first from the main, and later from the mirror site).
-flushed the caches of Firefox and Safari (which I use interchangeably).
-attempted to ssh the command "sync; echo 3 > /proc/sys/vm/drop_caches" as had been suggested on this thread by DonnyJohnny. It returned an error about echo3 [perhaps because I am on mac os, most likely because I am useless]
-flashed the fw from the administration/firmware upgrade page of the GUI
-As the machine requested a 'Manual reboot', I did power it off, unplugged it from the wall and let it rest a decent 5'. Took this opportunity to power-cycle my ONT too (getting internet via FFTH from a reputable - historical -provider in rainy Spain)
-Restarted the ONT. Waited.
-Restarted the router
-My old SSIDs were still showing. hmm.
-Bypassed the internet setup page and did a Restore to factory settings.
-Waited
-Joined the default ASUS_AO_2G network that had appeared [not sure this was the exact name].
-at some point it prompted for my ISP credentials, which I happily informed [those haven't changed in years]
-And then nuffin'... Stuck with the following screen
View attachment 13427
I attempted three times the above, to no avail. But -and I know this will raise some eyebrows-, I uploaded the settings I had saved from 384.4_2.
All seems to be fine and dandy now.
My apologies for the lengthy exposé. But if somebody could tell me what I have done wrong, I would much appreciate it.
-----
"Dear Asus Router: All praise to RMerlin, to whom all praise is due"
(In the way of J. Coltrane's Love Supreme)
But now you are still on 384.5 ?Hi all
Thought I'd share my frustrating experience attempting to upgrade to 384.5, coming from 384.4_2.
I attempted three times the above, to no avail. But -and I know this will raise some eyebrows-, I uploaded the settings I had saved from 384.4_2.
All seems to be fine and dandy now.
Thank you. That is what I did in practice, and so far so good...My 10 cents worth, going from one 384x version to another 384x version, I would just flash over the top & move on with life.
In my small experience, no need for back up/reinstall/restore in this instance.
The router is running 384.5 at present, and there doesn't seem to be any issue. Will try to re-input settings manually when I get the chance. Please can you specify what you mean by "Modem leave on synchronised all the time"?But now you are still on 384.5 ?
Which mode is choosen at the moment when working now?
Go to admin-page and reenter every single value to see if you loose connection bacause faulty setting.
Then do a factory again with initialize and wait much longer what will happen.
Modem leave on synchronized all the time.
That after initialize the router can find the modem with standing internet-connection. If you reboot modem same time it maybe not synchronized and so router will fail too.The router is running 384.5 at present, and there doesn't seem to be any issue. Will try to re-input settings manually when I get the chance. Please can you specify what you mean by "Modem leave on synchronised all the time"?
Thanks for taking the time.
Didn't notice any issue.Has this already been tested with the RT-AC86U? For me it is very unstable and strange and permanent disconnections on Android clients.
I've downgraded to 380.63 again (because I still had it there) and there everything is stable.
I asked if it was already tested with the RT-AC68U(not with the RT-N66U, or have you also a RT-AC68U?).Didn't notice any issue.
Has 384.5 already been tested with the RT-AC68U? For me it is very unstable and strange and and for some inexplicable reasons it can not be connected to some apps on Android clients.
I've downgraded to 380.63 again (because I still had it there) and there everything is stable.
because I know that 380.63 certainly works flawlessly and I did not feel like experimenting andWhy not go to 380.70 why such an old firmware?
Could you be more specific as to the issues?Has 384.5 already been tested with the RT-AC68U? For me it is very unstable and strange and and for some inexplicable reasons it can not be connected to some apps on Android clients.
I've downgraded to 380.63 again (because I still had it there) and there everything is stable.
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!