ASUS RT-N66U Firmware Version 3.0.0.4.374.2239

[bluepoint]

The driver I use is a custom build they provided me with.

I understand.

Regulation mode is something I implemented, it's not present in the stock FW.

Ah, I see no wonder I don't see it in stock. Thanks.

 

[tpackage]

Good for you! Okay please keep us posted.

One problem... I get the router working great but if I reboot the router it doesn't reconnect to the modem. I use a cloned MAC address... I get the feeling that when I reboot the router the MAC that is presented to the Modem changes and the connection can't be made. The only way I can get the router to connect again is to go through the Asus connection wizard and reboot the modem during the process. I have not had this problem in the past. I also notice that the router will go out on the network and randomly grab the MAC address of a device on my network and use that as a MAC for the ISP... I've never noticed that before.

Has anyone else had this problem with the -em version?

 

[bluepoint]

Is there any reason you're cloning the MAC? If it's really a problem with cloning the MAC and it's fixable, I'm sure Merlin or Asus will fix it. In the meantime, just use your router's MAC to avoid your problem. So you'll have a smooth transition, release your IP then disconnect the cable quickly before it request for an ip then unclone the MAC.

 

[tpackage]

Is there any reason you're cloning the MAC? If it's really a problem with cloning the MAC and it's fixable, I'm sure Merlin or Asus will fix it. In the meantime, just use your router's MAC to avoid your problem. So you'll have a smooth transition, release your IP then disconnect the cable quickly before it request for an ip then unclone the MAC.

I left the router running for a couple hours then rebooted and it worked fine. Not sure what the issue was. I'm just in the habit of using the same cloned Mac. I did find it interesting that the router would grab a Mac from another device if the Mac didn't work or if the field was blanked out.

 

[matman]

I have just updated to this firmware and it seems to have disabled my 2.4ghz wifi. Has anyone else had this problem?

 

[tpackage]

Good for you! Okay please keep us posted.

Did some more testing... .2239 on 5GHz seems to play nicer than -em with iOS devices... speedtest.net tests get up to top speed faster and max out more frquently. -em had some frequent super low test results. .2239 Seems to be more consistent with iOS. -em definately has better range though.

 

[MarkyPancake]

Installed 374.2239 today, but haven't finished configuring the settings yet. Will put it into action when I get back home.

 

[bluepoint]

Did some more testing... .2239 on 5GHz seems to play nicer than -em with iOS devices... speedtest.net tests get up to top speed faster and max out more frquently. -em had some frequent super low test results. .2239 Seems to be more consistent with iOS. -em definately has better range though.

Your speedtests use the same channel and channel bandwidth?

 

[tpackage]

Your speedtests use the same channel and channel bandwidth?

Yes, exact same configuration including channel and channel bandwidth. This was only something I noticed on newer iOS devices... laptops get the max speedtest ISP speed no matter what location I test from. I'm seeing the same thing today, iOS speedtests come back better in the location that matters most. That location is 31 feet away and one floor below the N66U router. That's important to me because most of my devices are hardwired... so Wi-Fi mostly supports smart phones and tablets and they are often in that location.

I also think iOS v7.0 has introduced lower Wi-Fi performance that hopefully will be improved in v7.1 soon.

 

[tpackage]

Is there any reason you're cloning the MAC? If it's really a problem with cloning the MAC and it's fixable, I'm sure Merlin or Asus will fix it. In the meantime, just use your router's MAC to avoid your problem. So you'll have a smooth transition, release your IP then disconnect the cable quickly before it request for an ip then unclone the MAC.

Today I had the same problem. I usually boot up the modem THEN the router. So when the router showed it was disconnected today after rebooting both modem and router, I left the router on and rebooted the modem again. After that the router connected fine.

 

[bluepoint]

What is your ISP? Is your modem in bridge mode? Do you still think the cloned MAC is causing the problem?

 

[msb]

Today I had the same problem. I usually boot up the modem THEN the router. So when the router showed it was disconnected today after rebooting both modem and router, I left the router on and rebooted the modem again. After that the router connected fine.

Comcast is my ISP and I boot the router before the modem as the modem looks at the router for the MAC to associate with, If the router isn't up, the modem doesn't associate.

 

[tpackage]

Comcast is my ISP and I boot the router before the modem as the modem looks at the router for the MAC to associate with, If the router isn't up, the modem doesn't associate.

That's what I'll do from now on. Comcast is my ISP... I figured that was the cause, but I didn't have that issue before or with my old Linksys router.

 

[jlake]

I tested this firmware and it seems to have pretty good wireless on both 2.4 Ghz and 5 Ghz with both range and throughput.

My unscientific quick tests concluded it's just as good as SDK5.

So good job Asus, better late than never.

 

[-AndyH-]

This beta f/w release stops IPv6 working with my ISP. I had to revert back to version 2050 for it to work again.

 

[tpackage]

This beta f/w release stops IPv6 working with my ISP. I had to revert back to version 2050 for it to work again.

What are you using IPv6 for?

 

[jim769]

What are you using IPv6 for?

I find it funny that some people are happy to use a firmware that brakes a function that the router was designed to provide. We are using v6 because we have it and can.

 

[tpackage]

I find it funny that some people are happy to use a firmware that brakes a function that the router was designed to provide. We are using v6 because we have it and can.

I was curious; I thought perhaps IPv6 was causing connectivity problems for you that may also apply to me. I didn't endorse anything being broken.

 

[-AndyH-]

I am trialling IPv6 for my ISP. Everything was working well until the beta upgrade....

 

[msb]

I am trialling IPv6 for my ISP. Everything was working well until the beta upgrade....

Who is your ISP? Comcast's IPv6 implementation works with this version of firmware here.