[Preview] Early Asuswrt-Merlin 384.6 test builds are available

[sn2018]

Have you rebooted the router, then tried?

Thanks.

 

[SMS786]

For one reason, I can't install this Alpha build. After I select the file and click "upload", a pop up windows with message "Please wait, Applying settings" pops up for a second or two before disappears.

Just fyi, I used to have the same issue. Now I need to unmount my usb drive whenever upgrading firmwares on my 68U.

 

[sn2018]

Main reason to try the alpha build is to see if the watchdog message still shows up every 30 seconds. They are...

Jun 26 17:21:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:22:18 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:22:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:23:18 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:23:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:24:18 rc_service: watchdog 300:notify_rc start_cfgsync

 

[skeal]

Main reason to try the alpha build is to see if the watchdog message still shows up every 30 seconds. They are...

Jun 26 17:21:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:22:18 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:22:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:23:18 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:23:47 rc_service: watchdog 300:notify_rc start_cfgsync
Jun 26 17:24:18 rc_service: watchdog 300:notify_rc start_cfgsync

I think this has something to do with your ovpn settings. That is if you are using ovpn at all...

 

[sn2018]

I think this has something to do with your ovpn settings. That is if you are using ovpn at all...

No ovpn.

 

[kfp]

I think this has something to do with your ovpn settings. That is if you are using ovpn at all...

Pretty sure this is AiMesh related, and known Asus bug. Unsure if fixed in latest GPL or alphas.

 

[skeal]

No ovpn.

Did you reset to factory after the flash?

 

[kfp]

Did you reset to factory after the flash?

That won’t help. I see those messages with 384.5 + factory reset + basic config in media bridge mode.

@sn2018 FWIW, I’m not seeing those messages after going from 384.5 to stock firmware 21045. So alphas *should* have it fixed as well but I’m not 100%.

Edit: I didn't realize sn2018 already flashed the alpha, thought he was just asking if it'll help with the log messages. Sorry @skeal

 

[sn2018]

I noticed this issue when I moved to 384.5 ( https://www.snbforums.com/threads/question-about-message-in-system-log.46985/ ) . I did not clear data when I installed the alpha build but I did when I installed 384.5. Messages still come out every 30 sec.

 

[kfp]

I did not clear data when I installed the alpha build

Yea you might want to do that.

alpha2 impression:
384.6 alpha2 looking good so far on HW rev 2.35 AC-RT3200, uptime 24hrs with no noticeable memory leaks. Both bands stable with Realtek devices and iDevices working fine. No disconnects. No spurious "br0 entered promiscuous mode" or "notify_rc start_cfgsync" in logs. No CPU pinned at 100%.

Dirty flashed over 384.6 alpha1 that I compiled myself with 8days uptime.

 

[Mihai]

When the asuswrt-merlin 384.6 alpha 2 will be available for rt-ac87u

Trimis de pe al meu ONEPLUS A3000 folosind Tapatalk

 

[scjr]

When the asuswrt-merlin 384.6 alpha 2 will be available for rt-ac87u

Trimis de pe al meu ONEPLUS A3000 folosind Tapatalk

He hasn’t received the GPL yet for that model:

https://www.snbforums.com/threads/p...-test-builds-are-available.47385/#post-413650

 

[bluepoint]

BUG
Adoptive QOS --->Bandwidth Monitor
Will crash miniupnpd everytime(repeatable)
RT-AC68P
1. AiProtection off
2. Adoptive QOS off
3. AiCloud 2.0 off
4. CTF + FA enabled

These logs shows when it happens.

Jun 27 00:59:38 kernel: Init chrdev /dev/detector with major 190
Jun 27 00:59:38 kernel: tdts: tcp_conn_max = 8000
Jun 27 00:59:38 kernel: tdts: tcp_conn_timeout = 300 sec
Jun 27 00:59:51 kernel: SHN Release Version: 2.0.1 3529123_patch
Jun 27 00:59:51 kernel: UDB Core Version: 0.2.14 r3529123
Jun 27 00:59:51 kernel: Init chrdev /dev/idpfw with major 191
Jun 27 00:59:51 kernel: IDPfw: IDPfw is ready
Jun 27 00:59:51 kernel: sizeof forward pkt param = 192
Jun 27 01:00:04 kernel: IDPfw: Exit IDPfw
Jun 27 01:00:04 kernel: mod epilog takes 0 jiffies
Jun 27 01:00:04 kernel: IDPfw: Exit IDPfw
Jun 27 01:00:05 kernel: Exit chrdev /dev/idpfw with major 191
Jun 27 01:00:05 kernel: Exit chrdev /dev/detector with major 190
Jun 27 01:00:05 rc_service: bwdpi_check 277:notify_rc start_firewall
Jun 27 01:00:05 miniupnpd[578]: shutting down MiniUPnPd
Jun 27 01:00:05 nat: apply nat rules (/tmp/nat_rules_vlan2_vlan2)
Jun 27 01:00:05 miniupnpd[1542]: HTTP listening on port 60485
Jun 27 01:00:05 miniupnpd[1542]: Listening for NAT-PMP/PCP traffic on port 5351

 

[kfp]

BUG
Adoptive QOS --->Bandwidth Monitor
Will crash miniupnpd everytime(repeatable)

These logs shows when it happens.

Jun 27 00:59:38 kernel: Init chrdev /dev/detector with major 190
Jun 27 00:59:38 kernel: tdts: tcp_conn_max = 8000
Jun 27 00:59:38 kernel: tdts: tcp_conn_timeout = 300 sec
Jun 27 00:59:51 kernel: SHN Release Version: 2.0.1 3529123_patch
Jun 27 00:59:51 kernel: UDB Core Version: 0.2.14 r3529123
Jun 27 00:59:51 kernel: Init chrdev /dev/idpfw with major 191
Jun 27 00:59:51 kernel: IDPfw: IDPfw is ready
Jun 27 00:59:51 kernel: sizeof forward pkt param = 192
Jun 27 01:00:04 kernel: IDPfw: Exit IDPfw
Jun 27 01:00:04 kernel: mod epilog takes 0 jiffies
Jun 27 01:00:04 kernel: IDPfw: Exit IDPfw
Jun 27 01:00:05 kernel: Exit chrdev /dev/idpfw with major 191
Jun 27 01:00:05 kernel: Exit chrdev /dev/detector with major 190
Jun 27 01:00:05 rc_service: bwdpi_check 277:notify_rc start_firewall
Jun 27 01:00:05 miniupnpd[578]: shutting down MiniUPnPd
Jun 27 01:00:05 nat: apply nat rules (/tmp/nat_rules_vlan2_vlan2)
Jun 27 01:00:05 miniupnpd[1542]: HTTP listening on port 60485
Jun 27 01:00:05 miniupnpd[1542]: Listening for NAT-PMP/PCP traffic on port 5351

Looks like it’s restarted (as opposed to “crashed”)?

 

[sn2018]

Yea you might want to do that.

...

Cleared NVRAM and still have the same message every 30 sec.

 

[kfp]

Cleared NVRAM and still have the same message every 30 sec.

You’ve flashed alpha2 already? Maybe try stock 21045?

 

[scjr]

2 1/2 days uptime on 384.6. It’s very stable and running really well. Impressive.

Nothing to do with Merlin, but I had issues with random disconnects on the higher 5GHz channels only and Apple devices. Testing this and thus far no issues with this GPL. Knock on wood. Either Apple updates or Asus solved the issue in this build.

 

[Magnus33]

68U running alpha 2 and very stable.

Much more so they my neighbor

 

[ablatt]

It's already merged:

https://github.com/RMerl/asuswrt-merlin.ng/commit/c9dd1802e8b3749dfe5aa638f2d3faff6368067d

Don't most of the change logs in the .zip downloads of the alpha 2 test builds say 20945?

 

[scjr]

Don't most of the change logs in the .zip downloads of the alpha 2 test builds say 20945?

Probably missed adding them, because he’s super busy.

GitHub is better way to check for changes.