RT-AC3100 Firmware.

[Deleted member 22229]

All i can say is 20942 is working rock solid for my 3100 no issues at all. I have it plugged in to my ATT gateway that is placed in IP pass mode and wifi disabled.

 

[DaveMishSr]

My 3 RT-AC3100's are functioning fine so far. I have one as the AiMesh router with 2 AiMesh nodes. I had been running 1 router with 2 repeaters while AiMesh got sorted out. After 48 hours the mesh has operated without issue. I love being able to run all QoS functions over the mesh. Bandwidth limiting is a handy feature when you have an adult child at home using both a Fire Stick & an Xbox One, often simultaneously.

 

[Quad80]

Something has to be wrong with my hardware, then. Asus support is kind of going in circles. Last email asked me to reset my modem and router. I've done that about a hundred times already, not sure where they're going at this point. I've been pushing for an RMA at this point, because I'm out of ideas and apparently so are they.

 

[DaveMishSr]

Something has to be wrong with my hardware, then. Asus support is kind of going in circles. Last email asked me to reset my modem and router. I've done that about a hundred times already, not sure where they're going at this point. I've been pushing for an RMA at this point, because I'm out of ideas and apparently so are they.

I had a bit of trouble too. I finally used my Surface and used a hardwired connection to the node (IPv4 set to a static IP & DNS) while my phone was connected to the router via WiFi. I also skipped the wizard on the node opting to manually set up the node instead. Once you click "next" on the node to begin setup then you immediately click "search" on the router.

That worked for me. Good luck!

 

[Quad80]

I had a bit of trouble too. I finally used my Surface and used a hardwired connection to the node (IPv4 set to a static IP & DNS) while my phone was connected to the router via WiFi. I also skipped the wizard on the node opting to manually set up the node instead. Once you click "next" on the node to begin setup then you immediately click "search" on the router.

That worked for me. Good luck!

Thanks, but this isn't an AiMesh issue. This is a "can't get DHCP to work in router mode when connected directly to the modem" problem. My other unit works just fine, but this one (which I practically took right out of the box) just isn't working. I've never, in all my years of setting up new routers, not had it just work out of the box. Given that I've factory reset the thing a number of times, rescued it, and tried a couple different firmwares on it now, it *has* to be hardware. I really don't have any idea how else it could be the software at this stage.

I've both used and skipped the wizard. It just doesn't work. With the wizard, attempting to click "automatic" just kicks it over to manual, because it doesn't work. Obviously manual doesn't work either, hence the hard stop on troubleshooting. Oh well. Things happen, I guess.

 

[DaveMishSr]

Thanks, but this isn't an AiMesh issue. This is a "can't get DHCP to work in router mode when connected directly to the modem" problem. My other unit works just fine, but this one (which I practically took right out of the box) just isn't working. I've never, in all my years of setting up new routers, not had it just work out of the box. Given that I've factory reset the thing a number of times, rescued it, and tried a couple different firmwares on it now, it *has* to be hardware. I really don't have any idea how else it could be the software at this stage.

I've both used and skipped the wizard. It just doesn't work. With the wizard, attempting to click "automatic" just kicks it over to manual, because it doesn't work. Obviously manual doesn't work either, hence the hard stop on troubleshooting. Oh well. Things happen, I guess.

Sorry. Should have read your messages through more closely. That's what happens when one multitasks with a unitask brain.

Hope you get it sorted. Does sound like RMA time. The 384 code is very wonky though. Many people are reporting strange issues. Stuff like yours in that your flying along fat, dumb and happy one minute and calamity rules the next. Or, one unit works great while another is a paperweight.

That is why now I avoid firmware upgrades. Before I would be all over Alpha & Beta releases knowing that if anything happened I could easily revert and use John9527's nvram utility to restore everything to as it was before. Now not so much.

I wish you luck and hope you get things sorted in short order!

 

[DaveMishSr]

30/30/30 isn't the standard overkill procedure anymore? I did that first, then a recovery to the new firmware, then another reset from the UI, after recovery uploaded the new firmware.

I'm not saying you're wrong, it's just since I've ever started dabbling with third party firmwares, 30/30/30 was always the most thorough and recommend action for a reset, so I'm surprised to hear otherwise.

What is the best way to reset this unit? Is it to hold the button for five seconds, or to do it from the UI? I've always thought hardware resets were preferred but maybe it doesn't matter anymore?

EDIT: To be clear, I'm not using third party firmware here. It's always Asus. I haven't even tried Merlin yet.

Several methods to perform a factory reset:

1) Use the initialize or restore button to clear everything in Administration|Restore/Save/Upload Setting.
2) With router off press and hold WPS button for 3-5 seconds, power on while holding button, continue to hold button and wait until the power LED flashes rapidly.
3) With router on press and hold the reset button for at least 5 seconds or until the LEDS go out signaling a reboot into the WAN setup.
4) with the router off press and hold the reset button for 3-5 seconds and power on while holding the reset button. Wait for the power LED to blink slowly indicating the router is now in recovery mode. You may now use the firmware recovery tool.

Big question is always the difference between restore and initialize. so...

Restore: Erases the Log / NVRAM
Initialize: Erases the Log / NVRAM / Database

And what does that mean...

The following explains what each area contains:

[Log]: System log , Offline client list, AiCloud log
[NVRAM]: Basic Setting Information
[Database]: AiProtection Monitor Log ,Traffic Analyzer Log , Web History

 

[Quad80]

So I did an RMA on my unit, because nothing I did could get it to recognize DHCP. It just came back today and the note was that they tested, couldn't replicate the error, and sent it back. Not a great start, but they did update to the latest firmware, so, okay, let's see what happens.

First, I had difficulty even getting the thing to set up. It kept cycling into the new network setup page after I set the network name, password, etc. I was hard wired to my old HP laptop using Chrome. It just would not let me proceed. I eventually tried IE, and it worked. So... okay, whatever. I got in, hooked it up to my modem aaaaand... same problem. It can't find the DHCP. Argh!

At this point, I'm ready to just go buy a new unit and return this one, because wtf. I power cycle everything, still no dice. I'm about to give up, I just power cycle the modem one last time, without cycling the router. Boom. It works. I have no idea how or why, but apparently cycling *just* the modem seems to allow it to work. Previously I was powering both down, turning on the modem, letting it settle, then powering on the router. This time I left the router on and it worked.

I couldn't tell you why that worked, I have no idea if it would have worked all those weeks ago when I first had these issues. I don't ever remember power cycling only the modem, but it's possible I didn't do this, as it seemed incomplete.

The RMA process was more than a bit painful, as they kept asking me to reboot, flash, and reset the router, which I had done dozens of times. When I finally got them to issue an RMA there were delivery issues at their warehouse and they didn't actually do anything. At least now I can say it seems to be working.

I'm going to try again to set it up completely and swap out my main router, to see if it will continue to work, but figured I'd update this thread.