384 not working with my AC3200

[cmkelley]

I've tried both 384.3 and 384.4 beta 3, neither will connect to the internet on my AC3200. Unfortunately, I got it downgarded to 380.69 just before Eric released 384.4 so I wasn't able to test it. I don't think my wife will put up with me trying again for a while ...

384 gives me the "Your ISP's DHCP does not function correctly" error. I hooked a (FreeBSD) laptop directly to the cable modem in the same port the 3200 plugs into and it got the public IP address no problem. I 'hard' reset both the modem and the router many times trying to get 384 to connect.

I was able to go back to 380 by flashing ASUS's firmware RT-AC3200_3.0.0.4_380_7743 from the gui, then hard reset, then Merlin's 380.69, then hard reset and it's back working. All of this was done without a hard reset on the modem. I didn't have to use the ASUS rescue tool, which seems odd given what Eric and others have said.

I'm wondering if something changed along the way ... my AC3200 was bought in April 2015, not long after its release. Anyone else with an early AC3200 have any luck with 384?

 

[jerry6]

Yes I have a very early 3200 and no problems with the 384 FW

 

[cmkelley]

Thanks Jerry.

 

[jerry6]

Thanks Jerry.

Could it be your ISP maybe turn everything off for an hour or so then try to connect . Can't see how 384 does not let you connect , did you factory reset and reenter all settings ?

 

[cmkelley]

Yep, re-entered everything by hand. More than once. Also had it all off for around 30 minutes, maybe more.

More importantly, it went from not working on 384 to working on 380 in less than an hour, without hard reseting the modem. Only unplugged the modem once, when I first loaded Asus's 380 and it went though the initial setup, it had me unplug it for a couple minutes, then replug it back in and retry discovery. Worked right away after that. Tried that countless times with 384 with no luck.

 

[AndreiV]

1) Search the forum for ""Your ISP's DHCP does not function correctly" error. " there will be 100's of entries.

2) Try flashing the official Asus firmware then going back to Merlin 384.

3) When you flash remove any USB device first .

 

[cmkelley]

I did try some of the forum (and other places on the internet) suggestions, including turning off DHCP in the modem before switching it to bridge mode with zero luck. In fact, with it working now with 380 I notably _didn't_ do anything to the modem except turn off its WiFi after the last hard reset. I'll search the forum directly before I try again, I was using google before.

ASUS has not released a 384 for the 3200. The latest is on their website is 382.50010. Of course in going back to Merlin 380, I did flash an Asus 380, but I haven't tried 384 since. As noted above, I'll have to wait until the wife's patience builds up again before I try. I don't have a spare router, I switched to the 3200 after rolling my own router on an old PC and pfSense.

Admittedly didn't try removing my USB stick. Definitely will do that next time.

Appreciate the help, I'm thinking I'll wait until Asus releases 384 for the 3200, then flash that and try Merlin's from there. For now 380 is working fine, I'm just a nerd who likes running the latest stuff, and of course wanting to make sure I plug security holes that pop up from time to time.

 

[cmkelley]

SITREP: I gave up. It would work for a while and then get wonky. I can only assume one of my cats sat on it and overheated something to the point it got to be intermittent with heat. So I grabbed apparently one of the last 86Us that Newegg had in stock (they're out of stock this morning). After spending a day fighting it I decided I spent way more of my time than it was worth.

Merlin, you made the choice easy for the replacement router - it had to be ASUS.