ASUS RT-N66U 3.0.0.5.354 Official Firmware

[Skywalker]

Why is de beta1 for 354 so much bigger in size than the 270 version?

 

[Skywalker]

Why is de beta1 for 354 so much bigger in size than the 270 version?

Hmm...confused it with something else....

Sorry... Keep up the good work RMerlin!

 

[Larsalex]

DNS Relay taking long time

Hi,

I was using .270 on my RT-N66U and whenever WiFi was connecting (after sleep) it took a long time (30 sec or so) before DNS lookups would succeed.
This happened on both OSX and Windows machines.
On OSX 'nslookup' would give 'REFUSED' during those 30 seconds.
Interesting is also that during those 30 seconds I could also not access the router's admin page (10.0.0.1).

Not being able to find a solution I jumped in and flashed to .354. This did not solve the problem. I went to factory settings. Did a reset of the ISP modem. Still the same. Then recently my ISP updated the ISP modem sw to allow 'bridge' mode. Even this did not solve the problem. It is driving me nuts.

When I bought the RT-N66U it was working fine. No idea what might have caused it.
I've tried defining multiple network locations on OSX. Tried using manual settings instead of DHCP.

Funny thing is that when I switch between LAN WiFi's, the problem still exists. But when I switch to guest network. DNS is working fine. No difference in WiFi settings though.

Once I changed the WiFi SSID. Right after connecting DNS was fine. After the first reconnect, the problem was back. Again, both Windows and OSX.

Anyone seen anything like this? Router logs don't show anything useful. Also not via SysLog.

 

[joegreat]

This happened on both OSX and Windows machines.
On OSX 'nslookup' would give 'REFUSED' during those 30 seconds.
Interesting is also that during those 30 seconds I could also not access the router's admin page (10.0.0.1).

Hi,

This sounds to me like a problem with the DNS servers from your ISP.

Just for testing purposes: Can you do a manual WAN configuration?
There you could enter the Google DNS servers:
8.8.8.8
8.8.4.4

And the test the DNS speed...

With kind regards
Joe

 

[Larsalex]

Hi,
This sounds to me like a problem with the DNS servers from your ISP.

Just for testing purposes: Can you do a manual WAN configuration?
There you could enter the Google DNS servers:
8.8.8.8
8.8.4.4

I've tried it and no change.
Thanks for the suggestion.

Lars

 

[Larsalex]

Ah, it seems I have finally found the source of the problem.
The Asus EA-N66...

I should have known. This device has caused problems before.
For some reason it seems to hijack the RT-N66U's 10.0.0.1 address.
Other times it does take the DHCP assigned address.
I've switched the EA-N66 from repeater to WiFi receiver mode only.
Still these problems.

You would expect these two similar branded devices would get along nicely...

 

[Larsalex]

Even after setting manual IP assignment in RT-N66U for the EA-N66
the EA-N66 still uses the 10.0.0.1 address. Even after a reboot.

So, now I've changed RT-N66U's IP address to 10.0.0.2.

Weird stuff.

 

[Trent Bates]

This is related to the 4.354 firmware but I didn't want to post the same in multiple places. Hope someone finds it helpful!

http://forums.smallnetbuilder.com/showpost.php?p=66640&postcount=274

 

[pjalexander73]

My System Log isn't showing any new entries except when changing settings. It use to log all dhcp leases and other things too. Ive emptied my browsers cache, Set the router to defaults by holding the WPS button for 10 seconds while starting up. Still a blank log. Anyone have any idea?