What's new

Asuswrt-Merlin 378.50 Beta 2 is out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-AC68U CFE still 1.0.1.6 ... how to force upgrade ?

Dec 1 01:00:22 kernel: !!! cfe_init !!!
Dec 1 01:00:22 kernel: cfe_init: CFE MTD 0 boot 0
Dec 1 01:00:22 kernel: cfe_init: block size 131072(00020000)
Dec 1 01:00:22 kernel: get_embedded_block:: mtd->size(00001000) erasesize(00080000) offset(00000000) emb_size(00020000)
Dec 1 01:00:22 kernel: cfe_init: cfe_nvram_header(cfba0400)
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_update: !!!! found !!!!
Dec 1 01:00:22 kernel: cfe_update: before fd0 f0
Dec 1 01:00:22 kernel: cfe_commit: done 0
 
I did this update to my 2nd AC68u today, it didn't update the bootloader again.

Still my bootloader was on 1.0.1.6. Then I flashed ASUS 3626 and the bootloader went to version 1.0.2.0 and after that I re-uploaded the 378.50b2. With the new bootloader seems I've fixed the problems described earlier, excepting the MAC Adress selection based on band
 
Still my bootloader was on 1.0.1.6. Then I flashed ASUS 3626 and the bootloader went to version 1.0.2.0 and after that I re-uploaded the 378.50b2. With the new bootloader seems I've fixed the problems described earlier, excepting the MAC Adress selection based on band

I had already done that, it was a FYI to merlin.
 
378.50 Beta 2 (31-Jan-2015)
- CHANGED: Moved the AC68U CFE update process to the same location
as in GPL 3626 to see if it works more consistently.


After the upgrade, CFE still shows 1.0.1.1


- FIXED: vsftpd wouldn't start if you had IPv6 enabled.

Indeed, no issues with that anymore.
 
First of all, a big big Thanks to Merlin!

And a small bug found, when adding names and static IP to devices by pressing the device icon:
Skärmklipp2.JPG

The DHCP page shows this:
Skärmklipp.JPG

The NAME for the added device is missing.

//Minglarn..
 
My RT-AC68R was in 376.48 before I flashed the 768.50_beta2. It all seems to be just great, the CFE bootloader is 1.0.2.0. Thanks Merlin!

Please take a look at AiCloud, I can't login to the web client with a 20 char password.
 
Last edited:
Regarding nmbd and smbd failing to start on my AC87U, I looked at the running processes on my AC66U and tried to start them manually:

Code:
/usr/sbin/smbd -D -s /etc/smb.conf
nmbd -D -s /etc/smb.conf

And now the services start OK. Some kind of race condition during boot perhaps?
 
Bootloader Ver

what bootloader version should my N66 be on when using this .50 beta2 F/W ?
 
Howdy folks,

A factory default reset is only required if you were not already running 378.50 beta 1.

Downloads are here.
Changelog is here.

Hi there.

Wait, what? I'm running 376.49_5 do I need to do a factory Reset before installing 378.50 beta 2?
 
Still having custom dns issues...

So, my no-ip address was working under beta1 but my afraid.org host wasn't.

installed beta2 & configured custon ddns setup to run my afraid.org script. as with beta1 the page hangs waiting for a response from the ddns-start script which never seems to run!

script is chmod 777 so should be readable to all...

Code:
admin@RT-AC66U:/jffs/scripts# ll
-rwxrwxrwx    1 admin    root           232 Jan 27 14:33 ddns-start*
admin@RT-AC66U:/jffs/scripts# cat ddns-start
#!/bin/sh

wget -q http://freedns.afraid.org/dynamic/update.php?Medited0 -O - >/dev/null

if [ $? -eq 0 ]; then

    /sbin/ddns_custom_updated 1

else

    /sbin/ddns_custom_updated 0

fi

manually running the script causes the DDNS page to respond with "registration successful" popup.

so, navigate back to home page and hostname appears there okay. try to navigate to said hostame from my phone, doesnt work. disable wifi so using cell coverage, page loads fine!!

RT-AC66U, although i would assume DDNS code common across devices

syslog for relevant events :

Code:
Feb  1 14:12:46 rc_service: httpd 373:notify_rc restart_ddns
Feb  1 14:12:53 watchdog: start ddns.
Feb  1 14:12:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:13:23 watchdog: start ddns.
Feb  1 14:13:23 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:13:53 watchdog: start ddns.
Feb  1 14:13:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:14:08 dropbear[560]: Child connection from 192.168.0.2:63303
Feb  1 14:14:23 watchdog: start ddns.
Feb  1 14:14:23 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:14:27 dropbear[560]: Password auth succeeded for 'admin' from 192.168.0.2:63303
Feb  1 14:14:53 watchdog: start ddns.
Feb  1 14:14:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:15:23 watchdog: start ddns.
Feb  1 14:15:23 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:15:53 watchdog: start ddns.
Feb  1 14:15:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:16:23 watchdog: start ddns.
Feb  1 14:16:23 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:16:53 watchdog: start ddns.
Feb  1 14:16:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:17:23 watchdog: start ddns.
Feb  1 14:17:23 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:17:53 watchdog: start ddns.
Feb  1 14:17:53 rc_service: watchdog 381:notify_rc start_ddns
Feb  1 14:18:04 ddns: Completed custom ddns update
Feb  1 14:30:02 dropbear[560]: Exit (admin): Exited normally
 
Last edited:
You should be able to use the utility described in the thread below to save your settings, and then restore them after the upgrade. I had a new router, so I ended up manually moving configuration info over from a router that was running different firmware.

http://forums.smallnetbuilder.com/showthread.php?t=19521

John

Will the 'Save Setting' under Administration work, or do I have to use the one in the link?
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top