I had the exact same amount of updates this morning weirdly enough. Seems to be working fine since I updated all of it.
Entware only publishes updates 2 to 4 times per year. Today was the day.Not sure why the update server didn't seem to be getting notified before today.
RT-AC86It must have been a while since you checked for updates. How old is your router and firmware?
Generally, it‘s OK to update.
That‘s why, I checked their website and to me there‘s no changelog published.Entware only publishes updates 2 to 4 times per year. Today was the day.
That‘s why, I checked their website and to me there‘s no changelog published.
Ultimate repo for embedded devices
A software repository for network attached storages, routers and other embedded devicesentware.net
IMHO it's not the responsibility of @thelonelycoder to approve or disapprove the installation of Entware updates. You are suggesting he is somehow personally responsible for testing every third-party addon script or Entware package, on every router, every time there's an update. That's clearly not practical. If you're concerned about a specific addon script I suggest you check the dedicated developer's thread for reported issues.The community is waiting for your approval and go ahead, once it reaches your server.
IMHO it's not the responsibility of @thelonelycoder to approve or disapprove the installation of Entware updates. You are suggesting he is somehow personally responsible for testing every third-party addon script or Entware package, on every router, every time there's an update. That's clearly not practical. If you're concerned about a specific addon script I suggest you check the dedicated developer's thread for reported issues.
That must be the case, because I couldn't see the logic in what I thought you were saying.No, you have taken what I said out of context.
I did jump in and install the Entware updates, primarily for the long awaited unbound updates. The only warning during the install was:Proceed with some caution with syslog-ng. There's some welcome new stuff (and a lot of bug fixes) moving from 4.7 to 4.10-2. I don't think it will break anything, but it could overwrite .conf so make a copy first.
Among other things, it introduces logrotate functionality within syslog-ng.
Collected errors:
* resolve_conffiles: Existing conffile /opt/etc/syslog-ng.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/syslog-ng.conf-opkg.
I found the same, having to check status in Scribe, which then updated and continued running.So far all looks good after the Entware update. Was surpised to see that just running Scribe and checking status
it does a sync and updated the version in syslog-ng.conf. Then restarts syslog-ng.
2026-04-07T11:03:04.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc stop_fw_check
2026-04-07T11:03:04.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
2026-04-07T11:03:05.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc start_fw_check
2026-04-07T11:03:05.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 11:31:57 syslogd started: BusyBox v1.25.1
Apr 7 11:31:57 kernel: klogd started: BusyBox v1.25.1 (2025-11-15 00:39:15 UTC)
Apr 7 11:31:58 rc_service: cfg_client 9941:notify_rc start_fw_check
Apr 7 11:31:58 custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 11:54:08 hostapd: wl0.1: STA 64:52:99:5a:a3:86 WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 64:52:99:5a:a4:3a WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 9c:43:1e:48:09:67 WPA: group key handshake completed (RSN)
Apr 7 11:54:08 hostapd: wl0.1: STA 54:e0:19:3c:11:85 WPA: group key handshake completed (RSN)
Apr 7 11:56:59 rc_service: cfg_client 9941:notify_rc stop_fw_check
Apr 7 11:56:59 custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
Apr 7 11:57:00 rc_service: cfg_client 9941:notify_rc start_fw_check
Apr 7 11:57:00 custom_script: Running /jffs/scripts/service-event (args: start fw_check)
Apr 7 12:19:48 dropbear[28360]: Child connection from 10.215.101.87:57578
Apr 7 12:19:48 dropbear[28360]: Pubkey auth succeeded for 'agagne' with ssh-rsa key SHA256:keSmX5Qw3wtl/V5acJCVnPuQizXAoRWJuNk0TlLjw/o from 10.215.101.87:57578
Apr 7 12:19:53 scribe:kill_logger[28512]: optmsg=[/opt/var/log/messages]
Apr 7 12:19:53 scribe:kill_logger[28512]: syslog_loc=[/tmp/syslog.log]
Apr 7 12:19:53 scribe:kill_logger[28512]: script_conf=[/jffs/addons/scribe.d/config]
Apr 7 12:19:53 kernel: klogd: exiting
Apr 7 12:19:53 syslogd exiting
2026-04-07T12:20:05.000000-04:00 xt8-garage dropbear[28360]: Exit (agagne) from <10.215.101.87:57578>: Disconnect received
2026-04-07T12:26:23.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc stop_fw_check
2026-04-07T12:26:23.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
2026-04-07T12:26:25.000000-04:00 xt8-garage rc_service: cfg_client 9941:notify_rc start_fw_check
2026-04-07T12:26:25.000000-04:00 xt8-garage custom_script: Running /jffs/scripts/service-event (args: start fw_check)
We use essential cookies to make this site work, and optional cookies to enhance your experience.