RT N66U firm. 3.0.0.3_151

[RMerlin]

I compiled a RT-N16 image of the 144 using your source.
was just a matter of calling make rt-n16

I did have some issues at first, but they were the same as I had to compile the rt-n66 image... Some bits are broken can't recall exactly the details now..

I think it was libusb and another lib that didn't compile properly

Ya, that was the theory - I just needed someone with an RT-N16 to actually flash it to confirm it was working (I wasn't sure all the binary-only drivers were included in my source tree). Now I have confirmation it's the case, so I might start pushing out RT-N16 builds as well.

I don't think my tester tried out the USB part - that's one thing I'll need tested once I make a wider beta release later today.

 

[richto]

Samba 4 is still in Alpha and emulates a version of AD 5 years old...

imo they should have split out emulation of AD from emulation of CIFS...

Dont expect even a beta of Samba 4 for at least a year imo.

 

[M3Rocket]

Try nslookup in a command prompt. For example, if your hostname is myhost.dyndns.org:



You will see if it returns an IP - make sure it's the same as your WAN IP.

You might also have more info on the System Log page.

For right now, it shows the same WAN IP since I cloned my 855's MAC. On the 855, I can tell it to update DYNDNS every so many minutes, and it will tell you whether the login and password works. I still can't tell on the Asus whether the login and password works. I assume it does not since the username and password fields still have a rex box around them eventhough I've tried several times to type in the username and password. Frustrating that something so simple, isn't.

Edit: I checked the logs, and it is indeed logging in successfully to DYNDNS. Except I still don't know where to set the frequency of the updates.

 

[richardeid]

Don't know if you tried it but Asus also released a .151 build for the RT-N16.

For me it seems quiet stable and the network discovery problem that .144 had are fixed.

http://www.asus.ru/ftp/NW_TO_TEST/RT-N16_3.0.0.3_151.trx

Sweet. Thanks. I'm pretty out of the loop. ASUS never - officially - released .112 for the RT-N16:

ftp://ftp.asus.com.tw/pub/ASUS/wireless/RT-N16/

But I'll guess that there was an official unofficial release of it somewhere. It seemed like all the rageThat FTP is pretty much what I keep my eye on. I catch up here, too, but most of the talk is for the N66U these days.

Anyway, yeah everything seems good with this one. So far the only thing I think I still have a problem with is the manual DST setting, but that's been going on since the release of the 3.x series of firmwares. Network discovery is also fixed up in this one.

A big one for me is logging. In previous releases the router wouldn't show or log packets that were passed inbound from the Internet. Those packets would be passed, but it would never show in the logs. For instance, I host a game server that listens for connections on port 7517. People could connect fine per my forwarded ports, but a log for those connect packets wouldn't be shown. If someone tried to hit, say, 7518 I'd see a blocked inbound packet logged...but never for actual packets that passed through. That's fixed up now. I think it was for .144, but I didn't stay on that one for very long.

All in all, I don't know if I've ever been more satisfied with a tech purchase. I bought this router coming up on two years ago now. It saw a pretty big slow down in development for a while, but all the features I ever needed worked fine, even before the switch to OpenWRT. So for me, the new UI was just icing on the cake. And everything that was ever advertised for this router still works (for me) as advertised. But obviously it's not just a new UI at this point. The features that have been extended towards the N16, even with all of ASUS's newer equipment available, is just...fantastic. Since moving towards Open WRT, here are a couple of new features I have that I didn't have before the move:

1. VPN server
2. Guest network (I guess I can ditch that second AP I was using.)
3. Real QoS (even if it's still a work in progress)
4. Traffic monitor (even though it's technically a part of the QoS feature)
5. Parental control
6. 3G failover
7. IPv6 (even if it doesn't work)

And I'll also throw out AiCloud, though I haven't used it yet. Some of the features look like something I could use in the future, so we'll see.

LOL, sorry for the pseudo-review. I'm just excited about the new stuff I have to play with. Anyway...thanks for the tip about .151 .

EDIT: Oh, also...the port forwarding bug with a "," in a rule breaking everything seems to be fixed in .151

 

[RMerlin]

For right now, it shows the same WAN IP since I cloned my 855's MAC. On the 855, I can tell it to update DYNDNS every so many minutes, and it will tell you whether the login and password works. I still can't tell on the Asus whether the login and password works. I assume it does not since the username and password fields still have a rex box around them eventhough I've tried several times to type in the username and password. Frustrating that something so simple, isn't.

Edit: I checked the logs, and it is indeed logging in successfully to DYNDNS. Except I still don't know where to set the frequency of the updates.

The firmware monitors your IP continuously. If there is any change in state, it will automatically update it on the DDNS service, rather than rely on regular external checks. In theory, you don't need a timer, as it's a continuous monitoring by the watchdog service. One worry I have however is how it handles DDNS services that will expire if there was no update in 30 days - I don't know if it has anything in place to force an update once in a while to avoid expiration of free services.

 

[jyavenard]

Ya, that was the theory - I just needed someone with an RT-N16 to actually flash it to confirm it was working (I wasn't sure all the binary-only drivers were included in my source tree). Now I have confirmation it's the case, so I might start pushing out RT-N16 builds as well.

If you checked the code provided for the RT-N56 and RT-N16, you'll find that it's all the same archive as the RT-N66.

They did a good job there... Going to make it much easier for them to support their hardware.
The RT-N16 uses the exact same hardware drivers as the RT-N66...

I still need to check how to enable the virtual SSID on the RT-N16, that feature is disabled, and I wanted to track what they are doing as the same feature in tomato is currently broken

 

[Gingernut]

FWIW on the latest .151 for the RT-N16 virtual SSID (guest network) is available and working, it won't let you make more than one from the ui though.

 

[RMerlin]

If you checked the code provided for the RT-N56 and RT-N16, you'll find that it's all the same archive as the RT-N66.

They did a good job there... Going to make it much easier for them to support their hardware.
The RT-N16 uses the exact same hardware drivers as the RT-N66...

I still need to check how to enable the virtual SSID on the RT-N16, that feature is disabled, and I wanted to track what they are doing as the same feature in tomato is currently broken

Unified code base is definitely the way to go, and it's nice that they went back and migrated existing devices like the RT-N16 to that codebase. Not only it makes it easier to develop and implement new features, but it also means that older devices don't get abandoned 6 months after they get to market. That has always been a major issue with Linksys devices for instance. How many Linksys/Belkin/whatever devices released at the same time as the RT-N16 are getting IPv6 support, for example? Probably not many, if any at all. Might mean fewer sales of new devices for Asus, but it also means more satisfied customers who are less likely to switch brand when comes the time to upgrade.

I was wondering if multiple SSID actually worked on the RT-N16, or if maybe it was a driver limitation. I see that multiple SSID availability isn't controlled by a build option but by device-specific init code in rc/init.c. Once I have a stable 144.10 release out I'll start looking at those features that are hardcoded in the code for newer devices only.

 

[Gingernut]

I've tested the guest SSID function on the RT-N16 using beta build .151 and it works well.

 

[RMerlin]

I've tested the guest SSID function on the RT-N16 using beta build .151 and it works well.

You said however that it won't let you make more than one. This would be a problem, since both features (multiple SSIDs and Guest networks) are tied together in the code.

 

[polpo]

Problem with static DNS

I have a static IP WAN connection and I'm having problems with DNS with .151. Lookups don't work at all. I telneted in and it looks like my DNS servers aren't getting populated into /tmp/resolv.conf. The file exists but is empty.

 

[Synomenon]

Is Asus ever going to post this on their support site?

 

[fredst]

I have a static IP WAN connection and I'm having problems with DNS with .151. Lookups don't work at all. I telneted in and it looks like my DNS servers aren't getting populated into /tmp/resolv.conf. The file exists but is empty.

I and many others have had the same problem.

Quickfix:

go into http://192.168.1.1/Advanced_WAN_Content.asp
make sure your DNS:es are populated.
click apply (even if they are populated correctly)
reboot

 

[fredst]

SMB problems

Hi

Wanted to report a prblem w 151

There seems to be a problem with transferring large files (>100Mb) from a MAC OS X 10.7 computer to a 3TB USB connected disk (on the n66u) over SMB.

 

[RMerlin]

Asus posted a build 155 on their Russian FTP server (see the other thread). See if it resolved your issues.

 

[Ramon]

When will Asus release the .151 version as their official? Does anyone know?
If i would upgrade the firmware using the beta version will i keep my guarantee?

 

[RMerlin]

When will Asus release the .151 version as their official? Does anyone know?
If i would upgrade the firmware using the beta version will i keep my guarantee?

Probably never, since they're up to beta 155 now. That new beta has AiCloud enabled, which is I suspect the reason for all these delays.

No problem regarding warranties - flash away

 

[Ramon]

Probably never, since they're up to beta 155 now. That new beta has AiCloud enabled, which is I suspect the reason for all these delays.

No problem regarding warranties - flash away

Thanks for the fast reply Merlin i appreciate! I think i will give it a go tonight. Gonna flash to version .151 or .155 since it was the last release.

##EDIT##

I flashed to version.155 since it was the latest test FW. So far it seems to work good. Better then .112 i had as my standard FW that came with the router.

 

[scajjr2]

I've noticed faster throughput since updating to .151. A 3Gb file transferred from my computer to our HTPC (Gb lan, path: my PC-Gb switch-RTN66U-HTPC) stayed at a steady 105mb speed.
Would start out around 90 then drop to about 60 using .108 .
Now if Comcast would get ipv6 going in my area so I can test that out on this router.

Sam

 

[richto]

155 posted now - dont bother with this version...