Asuswrt-Merlin 384.8 is now available

[wesbez]

Going to hang tight a while until 384.8 is more stable.

 

[Gar]

Reboot after all settings in place manually, first 10% of progress bar took a few minutes then resumed normally. All is working great however.

Don't recall reboot taking so long before, may be a one-time event and have nothing to do with this update. Afraid to try it again for now.

 

[predatorz]

Dirty upgrade from 348.8 to 348.8_2 on AC-88U successful.

 

[oso2276]

Upgraded RT-AC68U to 384.8_2. All working fine after a few hours

Enviado desde mi Moto Z2 Play mediante Tapatalk

 

[DroidST]

went to change QOS Que Discipline back to sfq after recent issues, then reboot from the gui.. didn't actually reboot even after several minutes (normally 86U reboot < 1 min) - lan4 led on, no other.

Hard Power Cycle back to normal.

Boy, was I spoiled on the 68u

 

[Martin_D]

Just updated the RT-AX88U to 384.8_2 All working fine

 

[EVO2point0]

Asuswrt-Merlin 384.8_2 has been released. Changedlog:

384.8_2 (8-Dec-2018)
  - CHANGED: Updated miniupnpd to 20181205.
  - CHANGED: Push LAN domain to OpenVPN clients as DNS suffix
             for the connection.
  - FIXED: Cannot save custom settings on OpenVPN server page
           on non-HND models.
  - FIXED: Some webui pages fail to load properly in French
  - FIXED: dnsmasq fails to start when certain options are
           configured (themiron)
  - FIXED: Non-functionnal Show Password option on OpenVPN/PPTP
           server page for RT-AX88U (removed)
  - FIXED: Persistent SSL cert was wiped at boot time in
           some specific scenarios.

Thank you.
I can confirm that the previously reported: OpenVPN "Apply" button not working with 384.8 is resolved with this new 384.8_2.
Thanks again for the update. Your work is greatly appreciated.

 

[consorts]

I have never been able to reproduce that problem here.

i think i figured out the problem...
tools/other.settings/misc.options/
new firmware version check NO,
when i set it to YES and then Apply
after a while the ! cleared

 

[Marin]

384.8_2 working fine here as well


Sent from my iPhone using Tapatalk

 

[kernol]

RT-AC5300 updated to 384.8_2 - all good ... many thanks

 

[TonyK132]

updated to 384.8_2 - working well. Thanks Merlin!

 

[bigcid10]

I upgraded from stock (newest )to 384.8_2 ,now my router refuses to open any ports from the port forwarding tab
I've tried rebooting,factory restore from within the ui and starting over
I'm stumped at this point
Thank you

 

[scjr]

I upgraded from stock (newest )to 384.8_2 ,now my router refuses to open any ports from the port forwarding tab
I've tried rebooting,factory restore from within the ui and starting over
I'm stumped at this point
Thank you

If you haven’t cleared your browser cache, give that a try.

 

[bigcid10]

If you haven’t cleared your browser cache, give that a try.

no dice
Is there a way to deadhead the router
maybe something is stuck.I can't open any ports

 

[saccleo]

dirty upgrade to 384.8 from 384.7
Are there are some differences?
1. using service restart_webdav will cause iptable rules that customed lost?
2. if /jffs/scripts/nat-start exits, pnp service make make this script run?
i put some shell commands in it, include add iptable nat rules and set up aicloud ssl certifications. after upgrade to384.8.2, I found this script runs again and again by checking in the syslog. i'm sure that it works fine before, even in 384.7.
i tried back to 384.7, problem still there. maybe a factory restore can solve the problem.

 

[Gar]

i think i figured out the problem...
tools/other.settings/misc.options/
new firmware version check NO,
when i set it to YES and then Apply
after a while the ! cleared

I didnt have to select Yes, it just quit on its own after a few hours. It may be after power cycle too.

 

[RMerlin]

I upgraded from stock (newest )to 384.8_2 ,now my router refuses to open any ports from the port forwarding tab
I've tried rebooting,factory restore from within the ui and starting over
I'm stumped at this point
Thank you

Open your browser console and look for any Javascript error. Most common issue is you have a client with an invalid hostname.

 

[bigcid10]

Open your browser console and look for any Javascript error. Most common issue is you have a client with an invalid hostname.

I'm using the current version of chrome(71)
and all my Port forwarding is being done in the router gui

 

[RMerlin]

I'm using the current version of chrome(71)
and all my Port forwarding is being done in the router gui

Browser version have nothing to do with it. You need to check for Javascript errors if you want to troubleshoot this. Port forwarding itself is definitely working properly in the firmware code, I use them myself (as well as thousand of other users out there).

 

[bigcid10]

Browser version have nothing to do with it. You need to check for Javascript errors if you want to troubleshoot this. Port forwarding itself is definitely working properly in the firmware code, I use them myself (as well as thousand of other users out there).

I'm not sure how to open the javascript console to check
ok,I guess I hit f12 ,but I don't see anything or don't know what to look for