Recent content by Bagman

Like I said upstream, you have two models, one with gimped firmware, and one without. They can be the same hardware, but give them different model numbers, and just sell the gimped one in the US, and the working one everywhere else. It wouldn't be the first time a company has sold regionalised...

In the meantime customers miss out on fixes and improvements, or have to have their channels cut and subsequent poor performance due to interference. Don't forget, this US lockdown settings aren't needed for a few more years, Asus could easily take another few months to do it right if they...

What Asus should do is lock down the country code if the CFE is listed as "US". If it's anything else, let the country code still be set correctly by the user. Then you relabel the US version with a different model number. It's ridiculous that Asus are obeying US rules to have a correctly...

The problem is that Asus are lazy, or else they would have one product for USA, and another for the rest of the world that can set country codes correctly. As it is, they don't even bother to have correct codes for Europe, and just lump a dozen countries under the "EU" banner, even though they...

Hmm, that gives me nothing at all. I looked though all the strings and got: So EU routers are not using the correct codes/channels in their respective countries under this new forced setting. Maybe there is some way to change this setting in the CFE to get Asus to set the correct channels?

Is there any way to read the bootloader settings from the RT-N66U to see what country codes are set by default?

Sooner or later, the people with the old SDK 5 may have to make do with the older feature set, if the new code from Asus doesn't work with SDK 5. Alternatively, it may be the case that Broadcom/Asus will eventually get their WiFi drivers fixed, and backporting to SDK 5 may become unnecessary.

I updated it yesterday where it went to Android 4.3 (it was new and I was setting it up for someone else), but I didn't install any updates after that. I assume it got all the updates it needed. I'll have to check next time I see the device, but at least if it's a known problem with the Nexus...

Dunno really, because I only had the Nexus here for a day (it wasn't mine) and I just ran it on 5ghz. I didn't really have time to do any testing. I don't see this behaviour on my wife's Nokia Lumia running WP8 on 5ghz.

I was using an RT-N66U with a Google Nexus 7 v2 on 5ghz, and when I got out of range, the Nexus 7 dropped the signal. Walking back into range (a few feet in front of the router), the Nexus would not pick up the signal again. Said that the wi-fi couldn't be seen even though it was still shown...

For what it's worth, I've had no problems with this version, and the wireless has been fine. I did the install, a factory reset, then manually re-entered all configuration info. I also remade all the connections on the wireless clients.

The Superhub has a had couple of years to get its issues worked out (though it still has plenty of them and some are due to hardware limitations). The SH2 is new and has plenty of new issues of its own. Unfortunately it's not some kind of panacea for the SH1 issues.

Try it anyway. You may find the Asus is so much better for wireless than the Superhub that your IP cameras no longer drop the connection.

Bad idea. Just put the Superhub into modem mode and use the Asus as a router. It will make your life much easier. IIRC, people tried the DMZ trick with the SH1 before it had modem mode, and it's still double-natting.

Let's see if they've actually fixed the wireless driver this time!