rt-n66u questions on fw routing differences

[ApK]

Hi everyone,

I recently got an RT-N66U and I've accumulated some questions which I hope are OK to combine in one post here.
I'm dizzy from trying to Google my way to answers across the various fora.
So hopefully you won't mind slogging through a rather long post.

1. I'm a long time DDWRT user and am happy and familiar with it's feature set, and would not be having any issues if DDWRT could run this router at full speed.
Does anyone here happen to know if a fix for the 24.Ghz band 65Mps limit is likely to come to DDWRT anytime soon, or is there a special current build that already addresses it reliably?

2. I'm trying to understand the different routing behaviors between DDWRT and the ASUS/Merlin FW.
My primary LAN is 192.168.2.0
I have a backup internal LAN, 192.168.3.0 running on an another DDWRT router with a VLAN port to act as the gateway, with an address of 192.168.2.3
With DDWRT on my main router, in the GUI, I can configure a static route between my two internal LANs by just entering 192.168.3.0 as the destination and 192.168.2.3 as the gateway. Once I do that, all clients on both LANs can communicate both ways.
With the ASUS stock or Merlin FW, if I do that, I can only hit the gateway address, no other clients are visible from the 2.0 lan, and clients on the 3.0 can't see the 2.0 lan at all.

I imagine this is related to the same behavior I see in several threads here where people cannot hit their cable/dsl config page unless they enter some startup commands, but I don't understand the details or why it seems be different on the different firmwares. For the last several versions of DDWRT I've been using, I can hit my off-segment cable modem admin address without having to run those commands. Without even a static route entry.

3. Lastly, I was thrilled to see that the stock firmware supported Zoneedit.com DDNS, but it doesn't appear to work for me.
The Zoneedit option in DDWRT also stopped working for me. Apparently URL changes at Zoneedit have recently forced me to use a custom DDNS setting on DDWRT.
Is the Zoneedit ddns working for others in the stock or merlin fw?
If not is there way to get it to work (besides installing a different DDNS client)?

Thanks for reading this far!

ApK

 

[ApK]

Digging around here more, I found info and a workaround on my most important issue, #2 above. The workaround is distilled into a single lovely command here:
http://forums.smallnetbuilder.com/showpost.php?p=73329&postcount=22
in case anyone else is looking for it.
I don't exactly understand the issue discussed in the thread, but it's gone now.....
So I can happily stay on Merlin's fw now!

I've had no luck finding anything recent about the Zoneedit DDNS issue.

ApK

 

[Myk]

I'm having issues with zoneedit also - looks like at least one other person @ DNS-O-Matic forums is also having an issue (via DNS-O-Matic)

https://support.opendns.com/entries/31437814-DNS-O-Matic-Appears-to-Be-Broken-With-ZoneEdit

I sent a support email to zoneedit to see if they have any input

As a sidenote I disabled dyndns until it's resolved as the error message overflows the log file pretty quickly, and I'm pretty sure caused a router crash last night for me

 

[ApK]

I'm having issues with zoneedit also - looks like at least one other person @ DNS-O-Matic forums is also having an issue (via DNS-O-Matic)

https://support.opendns.com/entries/31437814-DNS-O-Matic-Appears-to-Be-Broken-With-ZoneEdit

I sent a support email to zoneedit to see if they have any input

As a sidenote I disabled dyndns until it's resolved as the error message overflows the log file pretty quickly, and I'm pretty sure caused a router crash last night for me

Rats, I thought D-O-M would be the workaround for that issue. It didn't occur to me that they might have an issue with ZoneEdit, too. Well, hopefully someone is working on it over there.

I contacted ZoneEdit support last week about this, and they just sent me their knowledge base article on how to use their DDNS service, and closed the case.