Release Asuswrt-Merlin 386.2 is now available

[banger]

Hi @banger, how did you check the AP Uptime? I can't find this anywhere. I would like to check mine because it seems my node drops sometimes.

I used Winfi Lite on my PC which tells you AP uptime, also Wifi Analyzer from windows store is a free app which under the network tab tells you AP uptime.

 

[MvW]

Hi @banger, how did you check the AP Uptime? I can't find this anywhere. I would like to check mine because it seems my node drops sometimes.

Just login into your node using the same credentials you use for your main router and type:

uptime

and it’ll show you the uptime and some additional info like load average.

marco@RT-AC68U_WHITE7130:/tmp/home/root# uptime
19:13:23 up 2 days, 12:21,  load average: 0.21, 0.08, 0.06

 

[banger]

Just login into your node using the same credentials you use for your main router and type:

uptime

and it’ll show you the uptime and some additional info like load average.

marco@RT-AC68U_WHITE7130:/tmp/home/root# uptime
19:13:23 up 2 days, 12:21,  load average: 0.21, 0.08, 0.06

With all due respect that shows the OS Uptime not actual AP uptime which can vary.

 

[mmacedo]

I used Winfi Lite on my PC which tells you AP uptime, also Wifi Analyzer from windows store is a free app which under the network tab tells you AP uptime.

Winfi Lite is pretty cool. I can see my router and node 5G radios uptime:

 

[MvW]

With all due respect that shows the OS Uptime not actual AP uptime which can vary.

I wasn't aware there was a difference, but thanks for correcting me.

 

[banger]

I wasn't aware there was a difference, but thanks for correcting me.

Sometimes when making configuration changes to wifi sections the AP will restart. Sometimes it will restart all of its own right in the middle of streaming stuff without a reboot.

 

[banger]

Anyone got an email address for Asus to feedback the above post as stock firmware does the same after about 6 days uptime. 6 days is not bad but it would be better if AP was stable other than using the reboot scheduler.

 

[Deleted member 22229]

Sometimes it will restart all of its own right in the middle of streaming stuff without a reboot.

This is certainly not by design and not normal.

 

[banger]

This is certainly not by design and not normal.

I believe 384 branch was ok but there is a lot of security fixes under the bridge since then. Unless one tried 384 on the node and 386 on the router. Not sure Mesh will work.

 

[banger]

Trying 384.19 on the node. Mesh seems to work ok will monitor.

 

[ugandy]

This is certainly not by design and not normal.

but not unusual. i get it sometimes when I do a speed test and get close to 850Mbps (wifi restarts)

 

[Female]

I am also experiencing random restarts and weird behaviour since updating to 386.2

My AC86U is suddenly going mental! Anything I can do for her at this point?

xx

 

[askan7]

I've never seen USB transfer speeds soo slow as today with 386.2.

I knew they were like much slower than 384.19, but if a torrent client is running in any client it slows down to a crawl. With both cores to 100%, and that's with USB 2.0!!! Yes, 2.0 only, i switched to it because 386.2 was soo slow it caused ping spikes if someone was reading from USB. But even with USB 2.0 under some scenarios I get 100% cpu usage.

I tried disabling cake, made barely any difference.

Other than that, rock solid since beta 3.

 

[Deleted member 22229]

I've never seen USB transfer speeds soo slow as today with 386.2.

I knew they were like much slower than 384.19, but if a torrent client is running in any client it slows down to a crawl. With both cores to 100%, and that's with USB 2.0!!! Yes, 2.0 only, i switched to it because 386.2 was soo slow it caused ping spikes if someone was reading from USB. But even with USB 2.0 under some scenarios I get 100% cpu usage.

I tried disabling cake, made barely any difference.

Other than that, rock solid since beta 3.

Hang in there i see there is a 386.2.1 on the horizon. No commits made in two days not sure if it will help all the people with issues or not. No idea when this will be made public. I guess Merlin can only answer that.

 

[banger]

Trying 384.19 on the node. Mesh seems to work ok will monitor.

Bind option on the node has disappeared, but I suppose that is to be expected. Also if you change Firmware check to No there is no Apply button.

 

[Deleted member 22229]

Bind option on the node has disappeared, but I suppose that is to be expected. Also if you change Firmware check to No there is no Apply button.

384 code only has Amesh 1.0. 386 code has Amesh 2.0 mixing them will likely cause a headache. Reading all the issues people are having with the 386 code one would have to start thinking it's half baked at this point. Painfully long Alpha and beta stages are a obvious clue there are problems. Asus even quit responding to there own self stared Beta thread. Crickets.

 

[banger]

384 code only has Amesh 1.0. 386 code has Amesh 2.0 mixing them will likely cause a headache. Reading all the issues people are having with the 386 code one would have to start thinking it's half baked at this point. Painfully long Alpha and beta stages are a obvious clue there are problems. Asus even quit responding to there own self stared Beta thread. Crickets.

Yes I am aware of the differences between the 384 branch and 386 branches but it is a quick and dirty test of wireless stability.

 

[anotherengineer]

so far

Uptime	4 days 20 hour(s) 45 minute(s) 13 seconds

what are some good free tools to test home networking??

 

[RMerlin]

Anyone got an email address for Asus to feedback the above post as stock firmware does the same after about 6 days uptime. 6 days is not bad but it would be better if AP was stable other than using the reboot scheduler.

There's a Feedback form on the stock firmware.

 

[AlbumMan]

Thought I would jump in with my 2cents update... Very basic setup, no mesh and only a few 2.4 and 5G devices. Have been using 384.19 immediately since buying the RT-AX3000 (aka RT-AX58U) back in November and has been rock solid. When 386.x came out, I tried every beta but kept returning to 384.19 due to one 2.4 device randomly dropping/reconnecting; my LaCrosse Weather Station. Others have reported their Honeywell Thermostat doing this but mine has never failed. Each time updating, I've done the usual reset method only to have the LaCrosse drop randomly again. Now that 386.2 release is here, I gave this a try and magically, have had NO drops. Not sure if there was a change in the 2.4 wireless code but, fingers crossed, it still works after 5 days now.