[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[jrmwvu04]

If you switch to another gui page, and then back to the syslog page, did the logons continue while you are on the other page (that is, is this unique to the syslog page?)

No, it's not unique. A successful login (occasionally more than one) is logged on any of the GUI pages, even a simple browser reload logs another.

edit: If I sit and hammer reload in the browser, I'm reliably able to get this syslog output. Curiously, it occasionally peppers that nvram message in.

Apr 27 23:05:17 dropbear[2825]: Child connection from 192.168.1.50:54099
Apr 27 23:05:19 dropbear[2825]: Password auth succeeded for 'admin' from 192.168.1.50:54099
Apr 27 23:05:49 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:05:50 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:05:53 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:05:54 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:05:57 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:05:58 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:02 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:03 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:06 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:07 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:10 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:11 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:14 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:06:15 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:52 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:53 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:55 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:56 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:58 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:58 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:59 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:07:59 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:08:01 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:08:02 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:22 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:24 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:25 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:25 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:25 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:26 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:26 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:27 kernel: nvram: consolidating space!
Apr 27 23:09:28 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:28 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:29 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:29 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:34 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:35 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:46 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:47 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:47 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:48 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:49 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:49 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:49 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:50 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:50 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:50 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:50 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:51 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:51 kernel: nvram: consolidating space!
Apr 27 23:09:51 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:52 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:53 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:54 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:54 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:55 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:55 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:55 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:56 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:56 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:58 HTTP login: login 'admin' successful from 192.168.1.50
Apr 27 23:09:59 HTTP login: login 'admin' successful from 192.168.1.50

 

[jrmwvu04]

I fired up my Debian box to see if it was simply a browser issue. Using Iceweasel, browsed through several pages, reloaded several pages, no login messages in syslog. So at that point I installed Epiphany, or Gnome Web, or whatever they're calling it now because it's webkit based and guess what - successful logins galore. So whatever the issue is that causes this behavior, webkit plays some part it seems.

 

[john9527]

I fired up my Debian box to see if it was simply a browser issue. Using Iceweasel, browsed through several pages, reloaded several pages, no login messages in syslog. So at that point I installed Epiphany, or Gnome Web, or whatever they're calling it now because it's webkit based and guess what - successful logins galore. So whatever the issue is that causes this behavior, webkit plays some part it seems.

Not sure if this is the same....but sounds similar. (It starts with Safari 5.1, but the last post is last month).
https://discussions.apple.com/thread/3274071?tstart=0

EDIT: Forget the link

 

[jrmwvu04]

Not sure if this is the same....but sounds similar. (It starts with Safari 5.1, but the last post is last month).
https://discussions.apple.com/thread/3274071?tstart=0

EDIT: Forget the link

Well that is a bug nearly 5 years old so I won't be holding my breath I guess. Good news is that I go pretty rarely into the web GUI.

 

[jeff288]

Thanks John. QOS works great, just tested it with a B on the bufferbloat test compared to the previous F with it off. Always glad to see new features and fixes. My only issue, a very small one, is that on Firefox, system log > connections, it seems to fail the first or second time on refreshing. I set it to resolve domain names, btw. And here's my httpfox output if it helps. No big deal though, I'm happy with the firmware so far.

 

[wbennett77]

If the firmware is showing as V18B1, it means it took and you have the 64M rootfs.....so, one of two things....
For some reason NVRAM isn't being updated, or I'm mistaken on the CFE level for 64M support on the AC56U (1.0.1.9 was the initial release level, and I thought it was 32M rootfs).

To rule out the first case, ssh/telnet to the router and enter

cat /dev/mtd0 | grep bl_version

If that shows 1.0.1.9 also, I'm going to assume that the initial AC56U release also included 64M support and I'll update the doc.

Thanks for the 'test'.

Hey John,

Sorry for the delay but here is the info:

bl_version=1.0.1.9

Cheers!

 

[Chrysalis]

John I have cfe 1.0.2.0 but my jffs is 32meg, this is ok?

 

[john9527]

Hey John,

Sorry for the delay but here is the info:

bl_version=1.0.1.9

Cheers!

Thanks for checking.....I've updated the info in the Beta release post.

 

[john9527]

John I have cfe 1.0.2.0 but my jffs is 32meg, this is ok?

jffs for the AC68 is dedicated/fixed at 32M regardless of the rootfs size. No problem there.

 

[john9527]

that on Firefox, system log > connections, it seems to fail the first or second time on refreshing.

I remember seeing and researching this one (but I don't remember the details except for the result that it's a known limitation (bug?) on firefox when spawing system cmds for the first time on a page.. Since it does work on the second try, I didn't pursue trying to do any type of workaround (there didn't seem to be one documented anywhere). I wasn't able to recreate it on Chrome or IE.

 

[mobileman88]

My CFE on ac68u is 1.0.1.8 . I am currently on 17E8 . How should I upgrade to the new CFE? should i do the following?

- backup jffs and config in admin page
- upgrade to latest asus firmware as per https://onedrive.live.com/?authkey=!ALWnnK0vHDM91Wo&id=9332FC159A7E129!857&cid=09332FC159A7E129
- then flash back 17E8
- restore backup + jffs
- upgrade to 18B1

Thanks @john9527

 

[tuntun]

where is direct link to download this " RT-AC68U_3.0.0.4_374.43_2-18B1j9527.trx "....I can't see this inside link. thanks

 

[john9527]

Nope it does not work always on the second try .Something need to close and restart FF

I just tried it about 20 times in a row (closing and repopening firefox in between tries).....always works by hitting the refresh button a second time for me. Maybe there's an addon you are running that's making things worse?

 

[john9527]

My CFE on ac68u is 1.0.1.8 . I am currently on 17E8 . How should I upgrade to the new CFE? should i do the following?

- backup jffs and config in admin page
- upgrade to latest asus firmware as per https://onedrive.live.com/?authkey=!ALWnnK0vHDM91Wo&id=9332FC159A7E129!857&cid=09332FC159A7E129
- then flash back 17E8
- restore backup + jffs
- upgrade to 18B1

Thanks @john9527

The revelation that 1.0.1.9 on the AC56 had 64M support surprised me....so this will be interesting. It seems as if 1.0.1.8 is an EU only release, so this will be interesting. I'd do the following....

- backup jffs and config in admin page (always a good idea)
- upgrade to 376.3626 ASUS release and give things about 5 min to stabilize afterwards
- upgrade to the V18B1 code and again give it a few minutes to stabilize
- restore your jffs and config from step 1
- check your CFE level on the Tools>SysInfo page and please report back if it changed


.

 

[john9527]

where is direct link to download this " RT-AC68U_3.0.0.4_374.43_2-18B1j9527.trx "....I can't see this inside link. thanks

My fault, sorry. Microsoft has been messing up my OneDrive shared links, so I killed and recreated them all today, and accidentally put in the wrong link. Use this link to access my Beta folder
http://bit.ly/1SzwWvl

(Also updated in the Beta post).

 

[RMerlin]

Finding a GOOD distribution CDN is hard :/ They all have their own shortcomings.

 

[Chrysalis]

how would one switch this back to merlin's? and whats the difference between the two?

"0530101 nat: change default NAT loopback method from Merlin to ASUS"

 

[mobileman88]

The revelation that 1.0.1.9 on the AC56 had 64M support surprised me....so this will be interesting. It seems as if 1.0.1.8 is an EU only release, so this will be interesting. I'd do the following....

- backup jffs and config in admin page (always a good idea)
- upgrade to 376.3626 ASUS release and give things about 5 min to stabilize afterwards
- upgrade to the V18B1 code and again give it a few minutes to stabilize
- restore your jffs and config from step 1
- check your CFE level on the Tools>SysInfo page and please report back if it changed


.

CFE is now 1.0.2.0 . Thanks again

 

[mobileman88]

CFE is now 1.0.2.0 . Thanks again

somehow my optware has disappeared. how do i get it back without having to reinstall all the optware applications and settings?

 

[john9527]

how would one switch this back to merlin's? and whats the difference between the two?

"0530101 nat: change default NAT loopback method from Merlin to ASUS"

At a high level....Merlin's NAT loopback uses the mangle table and nat table and iptables marks to perform the loopback. ASUS method uses only the nat table without any iptables marks.

Using iptables marks can open one up to some problems if you write your own iptables marking rules without properly usings masks, or on the MIPS routers because of some limitations of using marks on the older kernel.

I haven't put it in the gui, but you can revert it to Merlin's NAT loopback by

nvram set fw_nat_loopback=0
nvram commit
service restart_firewall