Port forwarding and DMZ for rt-n66u?

[RogerSC]

I have an rt-n66u router with .108 firmware, and a Verizon Network Extender. If I use the Network Extender with my rt-n56u, and put it in the DMZ, everything is fine, the Network Extender comes up and works.

If I use the Network Extender with my rt-n66u, and either try to forward the right ports or put it in the DMZ, the Network Extender will not come up. This leaves me with a dilemma...I really want to use the rt-n66u since the wireless is better, but the DMZ and port forwarding don't seem to work. I could use tomato firmware, but I don't believe that the wireless would be as good as it is with manufacturer's firmware.

I don't see it, and doubt that it's there, but do you have to enable anything to use the DMZ on the rt-n66u? It just works on my rt-n56u so I doubt it, but you never know.

Have to admit that I'm a bit puzzled by this...I haven't seen any other reports of problems with the DMZ on the rt-n66u, so maybe I should just try reflashing .108? I've already tried resetting and rebooting, no help there. Has anyone else had problems with the DMZ on the rt-n66u, or am I the only one?

 

[RogerSC]

Now that I've had a few minutes to think about this, I'll bet that these (DMZ/port forwarding or something else that allowed the Network Extender to work) broke with firmware .108. I'll do some more testing in relation to this, probably on the weekend since I'll have to use the VPN to work tomorrow (actually, later today, time to call it a day *smile*).

But if I can verify that, I'll get in touch with Asus support. I shouldn't have to use the DMZ or port forwarding for the Network Extender, I didn't have to for the rt-n56u, which I did just verify, although it works in the DMZ with the rt-n56u (of course). It also worked fine with the DIR-655 and Linksys E4200 without needing DMZ or port forwarding.

*sigh* Maybe the .112 firmware is coming soon...there's reason to hope.

 

[mrcom]

here is the latest beta firmware .114 from asus http://www.4shared.com/folder/h9J1MTAx/_online.html
Here is another direkt link to the file http://www.tvestjartarna.se/RT-N66U_3.0.0.3_114.trx

 

[RogerSC]

here is the latest beta firmware .114 from asus http://www.4shared.com/folder/h9J1MTAx/_online.html

Thanks very much mrcom. I'm wondering if the md5 sum that I get from downloading this:

1A1CC6210AA7ADB857B9CA131773A4D7

matches the md5 checksum of your upload?

Thanks again.

 

[mrcom]

Thanks very much mrcom. I'm wondering if the md5 sum that I get from downloading this:

1A1CC6210AA7ADB857B9CA131773A4D7

matches the md5 checksum of your upload?

Thanks again.

How do i check this ? its Downloaded from asus and then uploaded to 4shared
EDIT newermind google is my friend check post below
best regards mrcom

 

[mrcom]

Thanks very much mrcom. I'm wondering if the md5 sum that I get from downloading this:

1A1CC6210AA7ADB857B9CA131773A4D7

matches the md5 checksum of your upload?

Thanks again.

here is my checksum
1a1cc6210aa7adb857b9ca131773a4d7 it seems to be the same

 

[RogerSC]

here is the latest beta firmware .114 from asus http://www.4shared.com/folder/h9J1MTAx/_online.html

Okay, I played with this a little, and the .114 Beta did seem a little better behaved. However, I think I may have messed things up by bringing up my work VPN during the time that the Network Extender was establishing its own VPN. The Verizon tech support guy told me that their Network Extender sets up a VPN, and uses that, and it can take about an hour to come up the first time (lame *smile*). If I had just left my work VPN alone until the Network Extender had come fully up it might have made it. Ran out of time to play with this today, and went back to the rt-n56u, which is fine for today.

I will play with this more over the weekend, and will try tomato as well if I need to. I'm curious how the wireless looks on that.

 

[RogerSC]

Okay, I played with this a little, and the .114 Beta did seem a little better behaved. However, I think I may have messed things up by bringing up my work VPN during the time that the Network Extender was establishing its own VPN. The Verizon tech support guy told me that their Network Extender sets up a VPN, and uses that, and it can take about an hour to come up the first time (lame *smile*). If I had just left my work VPN alone until the Network Extender had come fully up it might have made it. Ran out of time to play with this today, and went back to the rt-n56u, which is fine for today.

I will play with this more over the weekend, and will try tomato as well if I need to. I'm curious how the wireless looks on that.

I've verified now that the .114 Beta firmware, like the .108 firmware, doesn't allow the Verizon Network Extender to come up all the way. And Asus support has been informed, as well.

The .102 firmware does work with the Network Extender, as I had remembered.

I'll try tomato, too, if I get a chance.

 

[RogerSC]

I've verified now that the .114 Beta firmware, like the .108 firmware, doesn't allow the Verizon Network Extender to come up all the way. And Asus support has been informed, as well.

The .102 firmware does work with the Network Extender, as I had remembered.

I'll try tomato, too, if I get a chance.

I wanted to make a final comment on this in case it comes up in searches. If you have this problem with Asus firmware, the solution from Asus, to clear the nvram after upgrading the firmware, worked for me. Using the router's "reset" button apparently doesn't fully clear the nvram.

To clear the router's nvram, first enable telnet, then telnet into your router and use these commands:

mtd-erase -d nvram
reboot

This will completely erase the nvram and reboot the router. Of course you'll need to manually re-enter your router's settings after that. That allowed myNetwork Extender to come up. No DMZ or opening ports was necessary.