Release Asuswrt-Merlin 384.19 is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

RMerlin

Asuswrt-Merlin dev
Did full wipe of JFFS, and complete factory settings prior to isntalling384.19b2 then dirty upgrade to 384.19 final. One error keeps coming back up

Aug 15 08:28:06 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted
Not an error, just Linux`s typical way of saying it tried to load a kernel driver which wasn't needed.

Is a full factory reset needed or recommended going from .18 to .19 on an AX88U?
No, unless you notice anything unusual.

I have not enabled the persistent JFFS2 partition in my configuration.
It`s not something you can enable/disable, it's inherent to the firmware. Various settings are stored on that partition, so it's enabled for everyone.
 

martinr

Part of the Furniture
Now I have to go prowling the unbound thread to see if there is a way to backup its data so that it survives reboot/reflash.

Thanks, @RMerlin !!
I don’t want to get off topic, but is it not beneficial to occasionally dump the old cache and start afresh so it doesn’t get a build up of out-of-date dns resolutions?
 

L&LD

Part of the Furniture
@RMerlin, thank you for 384.19_0 release final. Great upgrade as usual.

@CaptnDanLKW, @Jack Yaz, and others, after upgrading every single RT-AC86U from 384.18 to 384.19_0 release final (almost 50 so far), the JFFS partition truncated to 47MB from 48MB caused issues either immediately or after a few minutes in the amtm scripts (showing minimal updates available when they're not, etc.), or, in the OpenVPN Servers and/or Clients. Waiting, rebooting, or full power off for a minute or two didn't solve these issues.

Upgrading from 384.18_0 or earlier and flashing 384.19_0 or later requires the steps outlined in the link below for stable operation.

I have no doubt that there will be some combination of options/features and scripts that don't seem to need the suggested steps below, but for 100% peace of mind, the minimal commitment to save the JFFS and then restore it after flashing 384.19_0 or later is worth it.


Note that I cannot edit the original post stating "... restore the JFFS partition 'if necessary' with 'required'..."

Restore the JFFS you saved after flashing to 384.19_0 to prevent unneeded wild goose chases on ghost issues that don't really exist. :)
 

Unetwork

Occasional Visitor
Hello, I have no backup of JFFS after flashing new firmware 384.19 I have the warning message. Should I format the JFFS to correct the problem? Thank you for the new firmware.
 

AnClar

Occasional Visitor
Dirty update of 384.18 to 384.19 on main router RT-AC5300 and three AIMesh nodes RT-AC68Us. All seems fine no issues after about an hour of uptime on all routers. Smooth sailing. Thanks again RMerlin!
 

L&LD

Part of the Furniture
@Unetwork, yes, format the JFFS partition and I would suggest you format the USB drive too on a PC to NTFS (if using one for the scripts) before you plug it back into the router.

Remove all USB drives/devices from the router.
Check the 'Format the JFFS partition on the next reboot' checkbox and then reboot the router 3 times in the next 15 minutes. Waiting 5 to 10 minutes after each reboot.

At the last reboot, wait 10 minutes for the router to settle fully and then insert the USB drive you formatted on a PC and format it according to Ext4 with journaling. Create a swap file of 2GB. Enable the disk checker built into amtm (dc).

Now, you can install the scripts you want.
 

jomcty

New Around Here
It`s not something you can enable/disable, it's inherent to the firmware. Various settings are stored on that partition, so it's enabled for everyone.
Thanks for the reply and update @RMerlin.

I didn't backup my JFFS since I assumed that only applied if the JFFS2 was being used. I don't see any adverse affects after the upgrade, and my JFFS using 22.29 MB of 47.00 MB. Should I assume the JFFS is corrupted and reconfigure, or since less than half of the JFFS is currently being used, it wasn't corrupted during the upgrade?
 

L&LD

Part of the Furniture

jsbeddow

Senior Member
Re: ASUS-RT AC68U - I want Wireguard. May we hope Dev will ever upgrade the kernel for Wireguard? Or I should buy AC86 for Wireguard?
In addition to the response from @RMerlin today, this Wireguard information has been extensively discussed for at least two years, see his response from April 2018 here in post #14 and #15:

Please use the search function of the site before registering just to post a question about a well discussed topic.
 

Unetwork

Occasional Visitor
@Unetwork, yes, format the JFFS partition and I would suggest you format the USB drive too on a PC to NTFS (if using one for the scripts) before you plug it back into the router.

Remove all USB drives/devices from the router.
Check the 'Format the JFFS partition on the next reboot' checkbox and then reboot the router 3 times in the next 15 minutes. Waiting 5 to 10 minutes after each reboot.

At the last reboot, wait 10 minutes for the router to settle fully and then insert the USB drive you formatted on a PC and format it according to Ext4 with journaling. Create a swap file of 2GB. Enable the disk checker built into amtm (dc).

Now, you can install the scripts you want.
@L&LD Thanks for your help. It's very sweet. After formatting JFFS and doing three reboots, is it necessary to reflash the firmware or not ?
 

CaptainSTX

Part of the Furniture
Dirty upgrade from 384.19b2 to 384.19 on my AC86. No issues two VPN clients and VPN server running along with all previously installed scripts.
 

RamGuy

Senior Member
Updated from 384.18 to 384.19 without any issues as usual. This is rather off-topic, but do anyone know what the required settings in order to get VoWiFi to work? Voice over WiFi has never worked for me when using my Asus RT-AX88U and Merlin firmware but when I was over at my parents house the past three days I noticed that their Google WiFi system gave me VoWiFi instantaneously and it was working all the time.

It's no biggie for me, I don't have that much use for VoWiFi. I'm just curious about whats lacking on my RT-AX88U for this to not work. We have the same ISP and I know for a fact that there is no limiting factor from the ISP itself and I have no firewall functionality on my AX88U that should be affecting this.

I can't seem to really locate any meaningful information on what kind of router requirements VoWiFi have? Some people claim that it won't work when you have hardware acceleration running in asus-wrt firmware aka flow cache but I have a hard time understanding why that might be a issue?
 

roundaway

Occasional Visitor
RT-AC66_B1 dirty upgrade from 384.18 to 384.19 without a problem. Removed the USB via the GUI, and then uploaded the file. 3-minutes later the router, diversion, and YazFi were back in business. Had a backup of the configuration and jffs just in case, but it wasn't needed. Thank you RMerlin.
 

Kanji-San

Regular Contributor
Updated from 384.18 to 384.19 without any issues as usual. This is rather off-topic, but do anyone know what the required settings in order to get VoWiFi to work? Voice over WiFi has never worked for me when using my Asus RT-AX88U and Merlin firmware but when I was over at my parents house the past three days I noticed that their Google WiFi system gave me VoWiFi instantaneously and it was working all the time.

It's no biggie for me, I don't have that much use for VoWiFi. I'm just curious about whats lacking on my RT-AX88U for this to not work. We have the same ISP and I know for a fact that there is no limiting factor from the ISP itself and I have no firewall functionality on my AX88U that should be affecting this.

I can't seem to really locate any meaningful information on what kind of router requirements VoWiFi have? Some people claim that it won't work when you have hardware acceleration running in asus-wrt firmware aka flow cache but I have a hard time understanding why that might be a issue?
I assume you mean WiFi Calling on your cellphone provided by the carrier when you say VoWiFi. It uses port 4500 and should automatically work. I am also using the AX88U with WiFi Calling. Depending on your carrier, it might only work if your signal strength is low. So if you have a strong cell signal in your house, you might never see WiFi Calling. Try to put it in airplane mode. This should definitely trigger WiFi Calling.
 

Sonyrolfy

Regular Contributor
Maybe its asked before, why did they removed that 1 MB from JFFS ? is there some advantage ? Dirty upgrade all working great! Thanks Merlin!
 

RamGuy

Senior Member
I assume you mean WiFi Calling on your cellphone provided by the carrier when you say VoWiFi. It uses port 4500 and should automatically work. I am also using the AX88U with WiFi Calling. Depending on your carrier, it might only work if your signal strength is low. So if you have a strong cell signal in your house, you might never see WiFi Calling. Try to put it in airplane mode. This should definitely trigger WiFi Calling.
Great recommendation! When going into airplane mode it activated itself immediately. So I guess it's do to the signal level.
 

Maverickcdn

Regular Contributor
384.16 --> 384.19 restore-->upload-->restore-->config

All is well...except my VPN config is borked on reboots now. I store my keys on the USB, its weird in that I have a 2.0stick in the 3.0 port as its not recognized in the 2.0 port. It is set to 2.0 mode.

Before on .16 all was fine, now on .19 the USB is loaded after the vpn is started so it fails to start
Aug 15 12:58:46 kernel: tun: Universal TUN/TAP device driver, 1.6
Aug 15 12:58:46 kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
Aug 15 12:58:46 kernel: device tap21 entered promiscuous mode
Aug 15 12:58:46 dhcp_client: bound mywanip/255.255.252.0 via mywanipgateway for 4002 seconds.
Aug 15 12:58:46 ovpn-server1[2182]: Options error: --dh fails with '/mnt/MAVNET16GB/vpn/dh2048.pem': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: Options error: --ca fails with '/mnt/MAVNET16GB/vpn/ca.crt': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: Options error: --cert fails with '/mnt/MAVNET16GB/vpn/MavNETVPN-SERVER.crt': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: WARNING: cannot stat file '/mnt/MAVNET16GB/vpn/MavNETVPN-SERVER.key': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: Options error: --key fails with '/mnt/MAVNET16GB/vpn/MavNETVPN-SERVER.key': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: WARNING: cannot stat file '/mnt/MAVNET16GB/vpn/ta.key': No such file or directory (errno=2)
Aug 15 12:58:46 kernel: tfat info: FAT32 volume name 'MAVNET16GB', version 0.0.
Aug 15 12:58:46 ovpn-server1[2182]: Options error: --tls-crypt fails with '/mnt/MAVNET16GB/vpn/ta.key': No such file or directory (errno=2)
Aug 15 12:58:46 ovpn-server1[2182]: Options error: Please correct these errors.
Aug 15 12:58:46 ovpn-server1[2182]: Use --help for more information.
Aug 15 12:58:46 openvpn: Starting OpenVPN server 1 failed!
Aug 15 12:58:46 hotplug[2022]: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/MAVNET16GB
Aug 15 12:58:46 usb: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/MAVNET16GB.

Ill find a way around it, just the one big thing I noticed
 

Jack Yaz

Part of the Furniture
Noticed an oddity earlier, which cleared after a reboot. Not sure why custom scripts said it was disabled, the WebUI page and the nvram setting both agreed it was enabled. Any ideas?
Code:
Aug 15 17:24:49 RT-AC86U notice rc_service: service 14724:notify_rc restart_dnsmasq
Aug 15 17:24:49 RT-AC86U alert custom_script: Running /jffs/scripts/service-event (args:  0)
Aug 15 17:24:49 RT-AC86U emerg custom_script: Found service-event-end, but custom script execution is disabled!
Aug 15 17:26:05 RT-AC86U info dropbear[17529]: Child connection from 10.14.16.40:44482
Aug 15 17:26:05 RT-AC86U info dropbear[17529]: Exit before auth from <10.14.16.40:44482>: Exited normally
Aug 15 17:26:19 RT-AC86U info dropbear[17854]: Child connection from 10.14.16.40:44158
Aug 15 17:26:19 RT-AC86U info dropbear[17854]: Exit before auth from <10.14.16.40:44158>: Exited normally
Aug 15 17:26:20 RT-AC86U err smbd[17857]: [2020/08/15 17:26:20.742139,  0] smbd/process.c:244(read_packet_remainder)
Aug 15 17:26:20 RT-AC86U err smbd[17857]:   read_fd_with_timeout failed for client 10.14.16.40 read error = NT code 0xc0000011.
Aug 15 17:26:21 RT-AC86U err smbd[17875]: [2020/08/15 17:26:21.263774,  0] smbd/process.c:244(read_packet_remainder)
Aug 15 17:26:21 RT-AC86U err smbd[17875]:   read_fd_with_timeout failed for client 10.14.16.40 read error = NT code 0xc0000011.
Aug 15 17:28:15 RT-AC86U notice rc_service: httpds 1346:notify_rc restart_time;restart_leds;restart_usb_idle;restart_firewall;restart_bhblock;
Aug 15 17:28:15 RT-AC86U emerg custom_script: Running /jffs/scripts/service-event (args:  1)
Aug 15 17:28:15 RT-AC86U emerg custom_script: Running /jffs/scripts/service-event-end (args:  1)
Aug 15 17:28:46 RT-AC86U notice rc_service: service 21040:notify_rc restart_dnsmasq
Aug 15 17:28:46 RT-AC86U emerg custom_script: Running /jffs/scripts/service-event (args:  1)
 

otaku521

New Around Here
just updated from 384-18 to 384-19

Have some issue with my AX88U

1) after a few seconds the screen and access to web ui freezes,
2) try refresh and it will not refresh...
3) tried rebooting my desktop - still no go
4) turn off router and then back to step 1 again


but I can get online just fine (posting this while online with this issue on my ax88u)
this works for both ethernet and wifi

and recommendations to remedy this?

1597524000023.png
 

Makaveli

Very Senior Member
just updated from 384-18 to 384-19

Have some issue with my AX88U

1) after a few seconds the screen and access to web ui freezes,
2) try refresh and it will not refresh...
3) tried rebooting my desktop - still no go
4) turn off router and then back to step 1 again


but I can get online just fine (posting this while online with this issue on my ax88u)
this works for both ethernet and wifi

and recommendations to remedy this?

View attachment 25458
There has been a few post about this on the earlier pages.

Leave it alone for 30 mins then check again.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

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