Asuswrt-Merlin 3.0.0.4.374.33 Beta 3 available

[Dilvish]

What 276 build?

For those wondering about 374_726: I was able to salvage most of the content of that corrupted GPL, and I didn't see anything worth waiting for, so I'm going ahead with the 720-based build for the time being. In any case Asus has been notified, so I would expect a fixed GPL 726 to appear on their website in the coming week.

I was referring to your comment quoted above. I must have been typing too quickly and transposed 726 to 276.

Sorry for the confusion and thanks for the quick reply!

 

[RMerlin]

I'm actually talking about the router's system log. The previous beta firmware has an entry about mips32r2 but now this is the only log showing.

"kernel: Time: MIPS clocksource has been installed"

The change has to do with how the compiler generates its binaries - it's not a FW feature or anything you would see in syslog.

root@ubuntu-dev:~/asuswrt/release/src-rt-6.x/router/mipsel-uclibc/target/bin# file busybox
busybox: ELF 32-bit LSB executable, MIPS, [U]MIPS32 rel2[/U] version 1 (SYSV), dynamically linked (uses shared libs), stripped

 

[RMerlin]

I was referring to your comment quoted above. I must have been typing too quickly and transposed 726 to 276.

Sorry for the confusion and thanks for the quick reply!

Just making sure, since there IS a build 276 too (from Asus).

There isn't much to be looking forward to be honest, since there are almost no differences between 720 and 726. The only visible changes I could see were two webui pages used by the Quick Internet Setup wizard, and some minor Makefile tweaks.

 

[pulp]

What am I forgetting? I select channel 1 but it keeps reverting to channel 6.
I hit Apply and even did a Reboot after Apply is not successful in locking channel 1.
inSSIDer confirms I'm stuck on overloaded channel 6, by neighbours. RT-AC66U

 

[RMerlin]

What am I forgetting? I selected channel 1 but it keeps reverting to channel 6.
I hit Apply and even did a Reboot after Apply not successful etc...

Just missing this

 

[pulp]

Just missing this

Now I'm really confused. I thought you had uploaded the fixed Beta 3 (because you mentioned it would be UL within half an hour and confirmed it was done, I think?) but kept the same name. So let me get this straight...

You do NOT have a beta3b out for my RT-AC66U?

 

[bluepoint]

Now I'm really confused. I thought you had uploaded the fixed Beta 3 but kept the same name. So let me get this straight...

You do NOT have a beta3b out for my RT-AC66U?

It's important that you specify the router you're having problem with, so Merlin will know which hardware you're talking about.

Please specify which router you are talking about when reporting anything

 

[krum]

Now I'm really confused. I thought you had uploaded the fixed Beta 3 (because you mentioned it would be UL within half an hour and confirmed it was done, I think?) but kept the same name. So let me get this straight...

You do NOT have a beta3b out for my RT-AC66U?

from Merlin response

"Will notify the thread once it's reuplaoded"

Chris

 

[pulp]

Okay...

Beta3b of the RT-N66U FW is now on Mediafire, properly recompiled for SDK6.

so Beta3 is different for different routers and the Beta3b *fix was just for the N66. I thought it was for all. Merlin Uploaded the fixed beta within the half hour he said he would, but it was only for the N66 and the timing was just too synchronicitious to be for realz.

 

[shrike4242]

Just to confirm, if I'm running the non-SDK6 version of 3.0.0.4.374.32 and I would upgrade to 3.0.0.4.374.33 when it's released, I should do a factory reset / clear NVRAM before doing the upgrade due to the SDK5.1 driver?

When I did my upgrade to .32, I didn't see that the SDK6 version of it was in the experimental section of the download library for the FW, so I'm on the SDK5.1 version of .32.

 

[oldgringo]

Okay...


so Beta3 is different for different routers and the Beta3b *fix was just for the N66. I thought it was for all. Merlin Uploaded the fixed beta within the half hour he said he would, but it was only for the N66 and the timing was just too synchronicitious to be for realz.

You can see it in changelog, AC66 uses SDK6 as a official revision for a longer period, N66U only from beta 3b build (excl. pixie dust builds).

 

[maycribb]

New SDK does that mean new wireless driver?

 

[brummygit]

Hi Merlin

Thank you for your new build - first impressions are very good on my RT-N66U.

I like the idea of Yandex, but everything is in Russian when sites get blocked.

There is a comparable free service from Symantec called Norton Connectsafe https://dns.norton.com/ would it be possible to include this in future builds. You simply need to use one of 3 pairs of DNS servers depending on the protection level required.

Thanks

 

[mikey]

Thanks as always for the new builds! Unfortunately just like the pixie dust version I tried a few weeks ago, this one has a massive drop in signal strength for the 2.4 Ghz radio. It's so bad that it's unusable for me. My phone and security cameras have intermittent dropouts in my back room which is max 50 feet away on the same level. So it appears I'm going to have to stick with 33 beta 1 on my RT-N66U until the WiFi driver is fixed on these newer SDK's. :-(

33 beta 1 signal level: -65 dBM
33 beta 3b signal leve: -90 dBM (with intermittent dropouts)

Oh, and just like the pixie dust version, cranking the output level up to 200mw (I usually run @100) makes no difference. I still think maybe that's a clue: maybe the signal level is "hard coded" to some lower level in the code somewhere?

Regards,
Mike

 

[jsmiddleton4]

I have same problem with this .3 beta as ASUS' release. I can not connect via 5ghz channel if I have any security enabled in the router for 5ghz.

Open system, connect fine via 5ghz and WPA2.

Previous 374.32 connect fine via 5 GHZ and WPA2.

Have done full NVRAM reset two ways, one with the option in the firmware and the other with power off, WPS held down, power back on, full hard ware reset.

Removed and rebuilt wireless profile.

Same result. Latest SDK6, my Broadcom 4322, even with what appears to be latest driver set, won't negotiate a connection via 5ghz wpa2.

My Windows 7 laptop driver gets to the place where it asks for the Password so the connection gets that far. When I submit it the router does not seem to recognize what is being sent so denies the connection.

Going back to 374.32......

 

[JGrana]

Client Status count and display incorrect

I have been seeing an issue with 3.0.0.4.374.33 both Beta 1 and Beta 3.

The Network Map page shows 2 clients and when I click to get the Client status list - it shows 2 clients.

I have more then 2 clients. The /var/lib/misc/dnsmasq.leases show 10 clients, which is pretty much correct. Oddly, they don't agree...

BTW, minidlna still crashes on Photo thumbnail generation. I didn't expect it to be fixed, but thought I would mention.

 

[jsmiddleton4]

Also when i do a site scan for wireless networks, no 5ghz networks show. Only 2.4ghz. I know there are 5ghz networks available. Mine and at least one neighbor has a 5ghz dual band router.

 

[pulp]

RT-AC66U

Okay, I went back to .33 Beta 1 because Beta3 didn't allow me to switch radio channels. I'm all good now. But why is beta 3 still in the RT-AC66U Mediafire Folder when it's buggy? That was part of my problem, besides being a n00b, I thought it would have been pulled.

 

[RMerlin]

Now I'm really confused. I thought you had uploaded the fixed Beta 3 (because you mentioned it would be UL within half an hour and confirmed it was done, I think?) but kept the same name. So let me get this straight...

You do NOT have a beta3b out for my RT-AC66U?

The problem only affected the RT-N66U, not the RT-AC66U.

 

[pulp]

The problem only affected the RT-N66U, not the RT-AC66U.

But what about my RT-AC66U and being stuck on Channel 6 with beta 3?