Asuswrt-Merlin 3.0.0.4.374.33 Beta 3 available

[RMerlin]

could you provide me with the code and steps to ssh in as i am useless at this type of thing

as far as I know is opening puttytel and logging into the router

Just plug the HDD back to your PC then and delete all the files that begin with ".__".

 

[Quiller]

Quiller, if you select AUTO and 20/40MHz, could you confirm it stays on your selected channel? If I select Channel 1, it disobeys me and locks onto 6, despite what the GUI shows.

I have to wait until my wife gets home with the old iPhone 3G. I have an app on that phone that can scan for wireless networks and that one can show the used channels too. I'll post that later.

 

[RMerlin]

I have got problem with minidlna in beta 3 which I hadn't in other versions.
Scanning operation doesn't stop and last record in log file is:
image_utils.c:419: warn: malloc failed

Known issue related to the artwork scanning that Asus has implemented in 374.720.

 

[RMerlin]

So somehow the DLNA server is blocking access to my drives in AiCloud! I don't have this problem with 3.0.0.4.374.33_beta1, so something is wrong with this build. I hope Merlin can fix it.

Most likely related to the DLNA integration with AiCloud that Asus implemented in 374.720. Not sure I can disable it since part of AiCloud is closed source.

 

[Quiller]

MP3 scanning

Known issue related to the artwork scanning that Asus has implemented in 374.720.

I had problems with mp3 scanning with the DLNA server before I switched over to Merlin's firmware. Some music albums wouldn't show up in my DLNA client at all and for some albums only a couple of songs were listed in the client. But a lot of albums were shown completely. I that read somewhere that miniDLNA needs ID3 Tag v2.3 for mp3's. So I checked all my music mp3's with MP3Tag (http://www.mp3tag.de/en/) and made sure that all of my mp3 files had that version.

I found out that iTunes doesn't handle album art very well and I use MP3Tag also for inserting album art in mp3 files. iTunes also doesn't create ID3 Tag 2.3, it creates ID3 Tag 2.2 mp3's as far I can remember. I don't use iTunes for creating mp3's anymore, I have to correct it everytime.

Now I have no problems at all with the scanning of my mp3 files.

 

[bluepoint]

According to the wireless log, it shows all our apple N devices Rx's speed are 24Mbps. I have not seen the speed above 24, however the actual download speedtest on the devices exceeds that speed or maximizes my service level which means the log is not accurate?

Note: Devices that are wireless G(iPhone 3G, PS3) shows 54Mbps Rx/Tx

RT-N66U
Firmware 3.0.0.4.374.33 Beta3b

 

[RMerlin]

According to the wireless log, it shows all our apple N devices Rx's speed are 24Mbps. I have not seen the speed above 24, however the actual download speedtest on the devices exceeds that speed or maximizes my service level which means the log is not accurate?

Note: Devices that are wireless G(iPhone 3G, PS3) shows 54Mbps Rx/Tx

RT-N66U
Firmware 3.0.0.4.374.33 Beta3b

Reported speed is dynamic, and will vary based on load, power management, etc... It should crank up to the maximum possible speed when you are actually transferring data.

 

[bluepoint]

Ok I'll observe more just to note the previous firmwares prior to .720 of yours doesn't exhibit this behavior, it shows more or less the connection speed and it's odd that the apple N products are the only ones limited to 24Mbps Rx speed measurement. It's probably the reason I notice it. If I may add, it shows on both bands.

 

[RMerlin]

Ok I'll observe more just to note the previous firmwares prior to .720 of yours doesn't exhibit this behavior, it shows more or less the connection speed and it's odd that the apple N products are the only ones limited to 24Mbps Rx speed measurement. It's probably the reason I notice it. If I may add, it shows on both bands.

The RT-N66U did change to a totally new wireless driver. I had been observing the same behaviour on both my AC66 and AC56, both also SDK6-based. So this could be a change related to SDK6.

 

[KAD]

going from beta 1 to beta 3 on RT-AC66U

WAN failed to obtain router and gateway

not a biggie, as I expected might need to clear nvram

after clear nvram, no issues

 

[bluepoint]

The RT-N66U did change to a totally new wireless driver. I had been observing the same behaviour on both my AC66 and AC56, both also SDK6-based. So this could be a change related to SDK6.

Makes sense its purely cosmetic but others might be scared of what they see.

 

[JGrana]

Known issue related to the artwork scanning that Asus has implemented in 374.720.

SabZeb - I had the same issue. As Merlin said, it's related to the Asus mods to minidlna. What I have done for now is install the older 1.0.25 minidlna using Entware:

opkg install minidlna

After reboot, I do a killall of minidlna (this kills the 1.1.0 minidlna processes):

# killall minidlna

then start up the 1.0.25 version that is now installed in /opt/bin:

# /opt/bin/minidlna -f /etc/minidlna.conf -R

Worked for me. Note - you will need to do this kill/restart after any reboot.

 

[Quiller]

Samba System Log - General Log entries I can't explain

Since I installed Beta3 I have these entries in my System Log:


Sep 24 20:33:28 nmbd[1926]: [2013/09/24 20:33:28, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Sep 24 20:33:28 nmbd[1926]: Samba name server ULTRALORD is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.1
Sep 24 20:33:28 nmbd[1926]: [2013/09/24 20:33:28, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 20:33:28 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 20:33:28 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 20:33:28 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 20:48:47 nmbd[1926]: [2013/09/24 20:48:47, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 20:48:47 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 20:48:47 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 20:48:47 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 21:03:53 nmbd[1926]: [2013/09/24 21:03:53, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 21:03:53 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 21:03:53 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 21:03:53 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 21:18:54 nmbd[1926]: [2013/09/24 21:18:54, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 21:18:54 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 21:18:54 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 21:18:54 nmbd[1926]: Unable to sync browse lists in this workgroup.

I don't how to fix this. I've reset the samba server, but this keeps popping up.

Thx for the help.

I'm on the AC66U.

 

[GoNz0]

Just plug the HDD back to your PC then and delete all the files that begin with ".__".

I did that and it didn't work, as another poster has done I turned off DLNA and it worked, turning back on and it didn't work. I deleted the following after showing hidden folders

.___var.txt
.___var142.txt
.__folder_list.txt
.__folder_list186.txt
.__GoNz0_var.txt
.__GoNz0_var142.txt

 

[jim769]

Tried Merlin 3.0.0.4.374.33_beta3-sdk5 I thought I could get the newer version with out the SDK6 driver but this firmware does not allow me to change the channel no matter what I enter it defaults back to auto channel 6. Any ideas? Had to go back to a older version now all is well. Im no expert but why is it so hard to get a good running firmware on the RT-N66R ?? There have been many new releases from Asus and Merlin and every one of them seem to have issues. Unreal.

I wanted to add that it did solve the 2.4 Ghz low signal issue that the SKD6 driver has. Why is Asus wanting to keep the SDK6 driver for the N66 I can understand for the AC66 but all my devices here including my 2 roku boxes don't like SKD6. I don't mean any disrespect but if Asus don't get a proper running firmware by the end of the year im going to try another brand router.

 

[RMerlin]

Tried Merlin 3.0.0.4.374.33_beta3-sdk5 I thought I could get the newer version with out the SDK6 driver but this firmware does not allow me to change the channel no matter what I enter it defaults back to auto channel 6. Any ideas I really figured there would be a issue but I tried it anyway. Had to go back to a older version now all is well. Im no expert but why is it so hard to get a good running firmware on the RT-N66R ?? There have been many new releases from Asus and Merlin and every one of them seem to have issues. Unreal.

Have you tried with your browser cache cleared (and even better with a totally different browser)? I remember a few months ago someone else had the same problem (it was with IE in his case), and the problem was caused by his browser who kept in cache some old webui elements from older firmwares.

 

[RMerlin]

SabZeb - I had the same issue. As Merlin said, it's related to the Asus mods to minidlna. What I have done for now is install the older 1.0.25 minidlna using Entware:

opkg install minidlna

After reboot, I do a killall of minidlna (this kills the 1.1.0 minidlna processes):

# killall minidlna

then start up the 1.0.25 version that is now installed in /opt/bin:

# /opt/bin/minidlna -f /etc/minidlna.conf -R

Worked for me. Note - you will need to do this kill/restart after any reboot.

I might not be able to fully disable that new functionality, but I could try to see if minidlna could be tricked in not scanning the files, leaving the database empty (which should keep the closed-source bits of AiCloud happy).

 

[RMerlin]

Since I installed Beta3 I have these entries in my System Log:


Sep 24 20:33:28 nmbd[1926]: [2013/09/24 20:33:28, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Sep 24 20:33:28 nmbd[1926]: Samba name server ULTRALORD is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.1
Sep 24 20:33:28 nmbd[1926]: [2013/09/24 20:33:28, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 20:33:28 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 20:33:28 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 20:33:28 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 20:48:47 nmbd[1926]: [2013/09/24 20:48:47, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 20:48:47 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 20:48:47 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 20:48:47 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 21:03:53 nmbd[1926]: [2013/09/24 21:03:53, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 21:03:53 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 21:03:53 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 21:03:53 nmbd[1926]: Unable to sync browse lists in this workgroup.
Sep 24 21:18:54 nmbd[1926]: [2013/09/24 21:18:54, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
Sep 24 21:18:54 nmbd[1926]: find_domain_master_name_query_fail:
Sep 24 21:18:54 nmbd[1926]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Sep 24 21:18:54 nmbd[1926]: Unable to sync browse lists in this workgroup.

I don't how to fix this. I've reset the samba server, but this keeps popping up.

Thx for the help.

I'm on the AC66U.

Looks like "ultralord" became the master browser, and it was rejecting the router's attempt at talking to it.

 

[RMerlin]

I wanted to add that it did solve the 2.4 Ghz low signal issue that the SKD6 driver has. Why is Asus wanting to keep the SDK6 driver for the N66 I can understand for the AC66 but all my devices here including my 2 roku boxes don't like SKD6. I don't mean any disrespect but if Asus don't get a proper running firmware by the end of the year im going to try another brand router.

Asus migrated from SDK5.100 to SDK.110 because it adds HW acceleration for PPPoE - something that is required from an increasing number of ISPs offering 200-300 Mbits over PPPoE, which cannot be achieved without CTF support.

Asus only migrated to SDK6 2 weeks ago, this was the first FW they released for the RT-N66U, and people are already ready to consider the switch to SDK6 a permanent failure.

Give them time. At least, unlike most competitors, they didn't tell you to just buy a new router if your old SDK5-based router was having issues with the XBox, or you had a 300 Mbits PPPoE connection that only ran at 100 Mbits because SDK5.100 lacks HW acceleration for PPPoE.

Those are two of the reasons for the switch to the newer SDK. And also I suspect that Broadcom isn't really interested in debugging the 5.xxx SDK anymore (we saw how well the 5.110 SDK worked out), while SDK6 is what is current, and therefore likely to be tweaked and improved in the coming months.

And it's not like you cannot run an SDK5-based firmware. Asus still offers 3.0.0.4.276 for this very reason. And I also offer an SDK5 based FW also for this reason. So if the newest firmware isn't fine-tuned well enough for your particular network yet, just run an older version, and wait.

Asus has shown a strong willingness in supporting their older products. Heck, the RT-N16U still gets FW updates. This alone is a very good reason for many of us to stick to their products. It might mean that some firmware updates might be a bit rougher around the edge as they go beyond simple bugfixing, and actually add new features and functionalities. But if people prefer stability over improvement, they are welcome to stick with an older firmware. Which is what you would get with the competition anyway, seeing how quick they are to stop supporting older products.

 

[jim769]

Fair enough Merlin you make some good points. I don't really have any issues staying with one of your older builds im using 3.0.0.4.372.32_Beta1 again now and it works perfect for all my devices and I have a quite a few of them. My issue is the future if there is a security issue I may be forced into a firmware that don't work well for me. Thanks for your reply. Jim !!