Posted: Fri Aug 26, 2016 13:25 Post subject: Can't reach LAN port clients
Got a N66U with latest stock firmware.
Flashed
dd-wrt.v24-30471_NEWD-2_K3.x-big-RT-N66U.trx
and everything seems to work perfectly...until i discover I can't communicate with anything on LAN ports from wifi clients (both bands). When I use Fing app on Androind it list all clients on LAN ports, but I can't ping them og communicate.
Is there any command or trick that fixes this?
Posted: Sat Nov 12, 2016 3:46 Post subject: Report on firmware update
Up to now I was running a hard-wired LAN, a private WiFi, and a guest Wifi SSID, with all 3 sharing the same LAN & DHCP server, on dd-wrt.v24-27360_NEWD-2_K3.x-big-RT-N66U.trx. Pretty stable, only needed reboots once a month or so.
For better privacy & security I decided to attempt an isolated subnet on the guest Wifi virtual SSID, but when I tried to set up new bridges & DNSmasq'ing for the isolated guest Wifi, I had problems with my router crashing and looping. I had to reset to defaults & load from a settings backup. (Make backups!)
So, I decided to risk new firmware and I updated to 30471. No problems with the FW update, and I did NOT do a 30/30/30. Just winged it & loaded v30471.
I got the guest Wifi network moved to a separate subnet, with firewall rules in place to block all traffic between subnets except for Guest Wifi <--> Internet access.
Also continue to have QoS enabled. Everything working smoothly so far, will update in a few weeks or months with longer-term stability report.
Posted: Fri Dec 16, 2016 18:38 Post subject: RT-N66U "Asus won't let you do that" message for D
Hi there. I purchased a pair of Asus RT-N66U's in order to run DD-WRT and, when I attempt to update to DD-WRT according to the DD-WRT installation instructions, I hit the issue with the Asus pop-up telling me it won't let me use an unauthorised software version.
I am attempting to load what I believe is the recommended version of DD-WRT (dd-wrt.v24-26138_NEWD-2_K3.x-big-RT-N66U.trx).
Others in here seem to have got away without hitting this issue. Any idea what I'm doing wrong?
FYI, I have tried doing the procedure that was recommended for the Sprint badged version:
...but that doesn't work for me either (the telnet CFE update step, which appears to complete successfully, shows the wrong version (1.0.1.9 as opposed to 1.0.1.6) after a reboot).
Try using the firmware restoration tool. A few months ago most router manufacturers included a check to prevent 3rd party firmware installation. _________________ I am far from a guru, I'm barely a novice.
S'OK, doing the rescue mode thing seems to have done the trick, though it was a fight to get into rescue mode. For the record, my successful procedure was:
1. With the router not connected to anything other than power, hold the reset button and switch the router on.
2. Wait for the power LED to flash (really slowly) and then release the reset button.
3. Connect a LAN Ethernet port to a PC where the PC's Ethernet port's TCP/IPV4 network properties have been assigned a manual IP address of 192.168.1.12 and a gateway of 192.168.1.1.
4. Start Chrome.
5. Go to chrome://appcache-internals/ and remove any entries for 192.168.1.1 or asus.
6. Browse to 192.168.1.1. You may have to wait some time for Windows to sort out what kind of network connection this is.
7. Eventually you should get an Asus mini-CFE web page which allows you to reset NVRAM and upload a new image.
8. Reset NVRAM.
9. Upload a "big" DD-WRT image, e.g. dd-wrt.v24-30949_NEWD-2_K3.x-big-RT-N66U.trx
10. Wait for it to upload and then for the wireless networking lights on the router to come on. This may take many minutes.
11. Press "continue" on the browser screen and you should see a DD-WRT screen.
Last edited by Rob Meades on Sat Dec 17, 2016 9:39; edited 1 time in total
The bits I was missing were (5), the waiting "for some time" part of (6), the "big" rather than "mega" in (9) and (0) "don't even bother with the Asus rescue tool, it never does nuffin" .
the restoration tool does work, you have to put the router into recovery state using the steps you already did. _________________ I am far from a guru, I'm barely a novice.
It timed out ("router is not in rescue mode") after 32 seconds every time for me, no matter what combination of resetting router with reset (or WPS, just for variety) pressed, plugging in Ethernet, starting application and restarting application I tried. You can probably blame Winders for taking its time doing stuff.