Signature update failed AC68U

[modemboy]

Trying to get the Trend Micro signature file to update on this router and having no luck. I suspect the Asus hosted update files are missing but would love some independent confirmation. I wasn't sure whether to post here or in the AC router section but I'm running Merlin 380.69_2 so I guess I'll start here.

When I go to Administration -> Firmware Update and hit the Check button next to the Signature Version (I'm currently on 1.110) it shows Signature Checking... and a spinning circle for ~5 seconds then I get Signature update failed. I've done a full nvram reset and even tried the sig check with no settings changed from default.

I took a look at the update scripts (even filed a bug on the new 2nd update script), and it appears to me the update script is working properly. This script: https://github.com/RMerl/asuswrt-me...ase/src/router/rom/webs_scripts/sig_update.sh

After I run the check from the web UI, get a sig_upgrade.log file in /tmp with contents
---- sig update real normal----
---- 1205 ---
---- sig_ver: 1205 ----

and the sig_state_flag gets set to 1 so that part seems to be working.

The upgrade script is where the problem happens I think. https://github.com/RMerl/asuswrt-me...se/src/router/rom/webs_scripts/sig_upgrade.sh

We can see in that script how the update URL is constructed (and I get --- wget fw Real ---- in the webs_upgrade.log file so I know it's making it to the wget line):
sig_file=`nvram get SKU`_`nvram get sig_state_info`_un.zip
and
wget $wget_options https://dlcdnets.asus.com/pub/ASUS/wireless/ASUSWRT/$sig_file -O /tmp/rule.trf

So the URL should be https://dlcdnets.asus.com/pub/ASUS/wireless/ASUSWRT/WW_1205_un.zip but if I manually go to that URL I get an error: An error occurred while processing your request.

So my question is, is that really the correct URL or is somehow my device getting the wrong SKU or sig_state_info value? And if it is the correct URL, is it working for anyone else? And if it is correct and not working how do I notify Asus to fix their file server?

Seems like the files went missing once before: https://www.snbforums.com/threads/aiprotection-signature-update-failed.28300/

But way more people were reporting the issue there so I'm worried this is a unique problem for me.

 

[RMerlin]

There seems to be a problem on Asus's end. I notified them, they are looking into it.

Update: They confirmed the problem and have fixed it on their end. Give it a day or so for the update to propagate.

 

[OMNI619]

Also try to factory reset your router and do it again

Sent from my SAMSUNG-SM-G920AZ using Tapatalk

 

[RMerlin]

Also try to factory reset your router and do it again

There's no need to try anything - the issue is on Asus's end, and they have already corrected it. It will just take a few hours before the changes propagate throughout their servers.

 

[OMNI619]

Believe me some times you still get the errors on your end because Asus fixed doesn't mean your 100% good to go you have to do some trouble shooting on your end

Sent from my SAMSUNG-SM-G920AZ using Tapatalk

 

[ankhazam]

Ok, interesting case....

Tested on AC87U 380_69.2 today:
1.202 Updated : 2018/01/21 02:00
Signature is up to date

Shouldn't it be 1.205 and today's date?

 

[RMerlin]

Ok, interesting case....

Tested on AC87U 380_69.2 today:
1.202 Updated : 2018/01/21 02:00
Signature is up to date

Shouldn't it be 1.205 and today's date?

I don't know what the actual error was, maybe it was that 1.205 was advertised when latest is really 1.202.

 

[HarryH3]

Ok, interesting case....

Tested on AC87U 380_69.2 today:
1.202 Updated : 2018/01/21 02:00
Signature is up to date

Shouldn't it be 1.205 and today's date?

I'm running the same version of Merlin on an AC68U, but it shows the current version as 1.180 and "Signature is up to date". Are the versions different for different routers?

 

[TLITD]

I have 2 AC68U routers, 1 running Merlin and 1 stock Asus. I have the latest firmware installed on each router, (Merlin: 380.69_2 and Asus: 3.0.0.4.384_20308-gead790e). The Signature Version on the Merlin firmware is 1.202 and on the Asus firmware it's 2.054.

A couple of months or so back I noticed that the Merlin and Asus Signature Version numbers usually matched after I updated them but more recently noticed (approx. 1 month or so) that the Asus Signature Version was updating more frequently than the Merlin Signature Version.

 

[Jack Yaz]

I have 2 AC68U routers, 1 running Merlin and 1 stock Asus. I have the latest firmware installed on each router, (Merlin: 380.69_2 and Asus: 3.0.0.4.384_20308-gead790e). The Signature Version on the Merlin firmware is 1.202 and on the Asus firmware it's 2.054.

A couple of months or so back I noticed that the Merlin and Asus Signature Version numbers usually matched after I updated them but more recently noticed (approx. 1 month or so) that the Asus Signature Version was updating more frequently than the Merlin Signature Version.

That's because the Asus stock is on 384 with the newer engine for Trend Micro

 

[HarryH3]

I have 2 AC68U routers, 1 running Merlin and 1 stock Asus. I have the latest firmware installed on each router, (Merlin: 380.69_2 and Asus: 3.0.0.4.384_20308-gead790e). The Signature Version on the Merlin firmware is 1.202 and on the Asus firmware it's 2.054.

Hmm. Mine still is at 1.180. When I click Check, the icon spins for a few seconds and it says all is well. The syslog only shows:

" rc_service: httpd 11187:notify_rc start_sig_check"

 

[modemboy]

Yeah the sig update zip file (not really a zip) provided by Asus is now messed up it seems, it only contains one value that is invalid: RT-AC87U#9.999
https://dlcdnets.asus.com/pub/ASUS/LiveUpdate/Release/Wireless_SQ/sig_update.zip

Don't think Asus fixed it properly. Firmware reports sig up to date but that's because there is no value except for the AC87U. I'm stuck on 1.110

Jack Yaz is correct there is a different update script for the 384 firmwares. That file has:
WW_FULL#2.992
WW_PART#2.992

 

[TLITD]

That's because the Asus stock is on 384 with the newer engine for Trend Micro

Thank you Jack!

 

[skeal]

When I check for updated signatures this happens:

Feb 12 11:37:37 rc_service: httpd 428:notify_rc start_sig_check
Feb 12 11:37:40 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:37:40 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:37:46 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:37:46 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:37:57 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Feb 12 11:37:57 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Feb 12 11:37:57 kernel: ioctl_iqos_op_config() fail!
Feb 12 11:37:57 kernel: ERR[qos_start:3344] QoS is already started!
Feb 12 11:37:57 kernel: ioctl_iqos_op_switch(1) fail!
Feb 12 11:37:58 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:37:58 kernel: Dead loop on virtual device vlan3000, fix it urgently!
Feb 12 11:39:43 syslogd started: BusyBox v1.25.1
Feb 12 11:39:43 kernel: klogd started: BusyBox v1.25.1 (2018-02-11 12:35:29 EST)
Feb 12 11:39:43 dropbear[17559]: Running in background
Feb 12 11:39:43 nat: apply nat rules (/tmp/nat_rules_vlan3000_vlan3000)
Feb 12 11:39:44 custom_script: Running /jffs/scripts/firewall-start (args: vlan3000)
Feb 12 11:39:45 Skynet: [INFO] Startup Initiated... ( banmalware autoupdate usb=/tmp/mnt/EXT2 )
Feb 12 11:39:45 hour_monitor: daemon is starting
Feb 12 11:40:07 Skynet: [Complete] 118606 IPs / 2044 Ranges Banned. 0 New IPs / 0 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [22s]

Something is pretty messed up!

 

[modemboy]

Update: They confirmed the problem and have fixed it on their end. Give it a day or so for the update to propagate.

Was the fix to just stop supporting older devices? Hope not but it appears almost intentionally broken for the older 380 build update script.

 

[RMerlin]

Was the fix to just stop supporting older devices? Hope not but it appears almost intentionally broken for the older 380 build update script.

Not that I know of. I initially received conflicting information, first I was told that signature support had ended on December, then I was told that signatures were still being updated, but they might be dropped at any time, and therefore people should start planning the move to 382/384.