Unfortunately Kongs firmware does not work properly for me in bridge mode. Client bridge mode is incredibly slow on the interface set to AP mode, and repeater bridge mode causes the router to bootloop if I reboot it or restore settings (if I even get it set up at all, most of the time I will not be able to select channels on the interface set to AP mode).
With brainslayer I don't have those issues, but overall performance of the wireless interfaces is not very good. I guess I'll have to stick to two separate routers for my needs for now.
I flashed Kongs firmware. Its not booting and I cant get in to recovery mode. I am powering on the router with the red button held down. Instead of blinking, the LED on the left turns off.
I cannot ping the router, so I cannot tftp. What options do I have?
Edit: powering up the router with wps held, then switching to the reset button gets the power led blinking. Still no ping, and it cant be found by the recovery utility.
Am I going to have to use serial recovery? Where can I find a procedure for that?
Google dd-wrt serial recovery.
Set a static ip on your computer and set a continuous ping. Ping 192.168.1.1. -t.
Then before turning on the router hold the reset button in then turn it on. When the ping response is ttl=100 it is in recovery mode. Then you can try to flash firmware using the mini cfe web server or use tftpd32. _________________ I am far from a guru, I'm barely a novice.
Turns out, it fixed itself after being left in recovery mode for over 24 hours. I've seen this router do the same thing with other firmware, but only taking about an hour. Wonder if it's just my unit, or if the model itself is just strange.
For future reference if anyone else has this problem. Flash the firmware, let it reboot. Power off.
Hold the WPS button and power on.
When the power LED flashes quickly, press and hold the reset button and release the WPS button.
The power button will blink slowly.
Keep a terminal pinging 192.168.1.1 while you do this. If it's stuck in boot loops, the output will switch between "timeout" and "unreachable". Just let it do its thing for an hour, or overnight, or a day.
Kinda sucks, but I'm happy to not have to open the router. And DDWRT works great!
Turns out, it fixed itself after being left in recovery mode for over 24 hours. I've seen this router do the same thing with other firmware, but only taking about an hour. Wonder if it's just my unit, or if the model itself is just strange.
For future reference if anyone else has this problem. Flash the firmware, let it reboot. Power off.
Hold the WPS button and power on.
When the power LED flashes quickly, press and hold the reset button and release the WPS button.
The power button will blink slowly.
Keep a terminal pinging 192.168.1.1 while you do this. If it's stuck in boot loops, the output will switch between "timeout" and "unreachable". Just let it do its thing for an hour, or overnight, or a day.
Kinda sucks, but I'm happy to not have to open the router. And DDWRT works great!
Your instructions are not the correct procedure.
Try all other official methods which should work. _________________ I am far from a guru, I'm barely a novice.
Last edited by Malachi on Wed Aug 01, 2018 21:34; edited 1 time in total
Joined: 08 Jun 2010 Posts: 109 Location: New Zealand
Posted: Wed Aug 01, 2018 20:11 Post subject:
What's the latest consensus on this router in terms of stability and compatibility with dd-wrt and KONG builds?
I am getting some spotty coverage using my Asus RT-AC68U on the 2.4ghz band and I'm wondering if I will get better performance/range with the AC-3200?
The critical functions for me are:
Routing with 2.4 and 5ghz support
Softether and/or IPSec server support
I recently tried an Asus RT-AC87U and while the radios were good, there were massive issues with missing features and functionality when it came to using DD-WRT (no softether in BS builds for the 87U). The 87U was also excruciatingly slow to flash and reboot. I ended up returning it.
So I'm wondering if the AC-3200 would be a good replacement for the venerable and stable RT-AC68U?
