What's new

[Coming Soon] New version notification system

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
s.2016-12-03 14.07.24.jpg


Firmware Version: 380.64_alpha3
Release note:

[*] Updated documentation.

[*] webui: fix App popup for Firefox (and probably other browsers), also resolve JS error on these browsers.

[*] build: fix building with AUTODICT disabled (closes #1102).

[*] tor: route other ports than just 80/443 through Tor, and block UDP/ICMP traffic (Closes #1118).

[*] openvpn: Updated to 2.3.13.

[*] webui: add link on the FW update page pointing to the enable/disable option on Tools->Other Settings; hide the field if firmware does not support live update.

[*] webui: have the new FW changelog page point you at your router's model download location instead of the primary landing page.

[*] Bumped revision to alpha 3.
 
I like it. It almost forces you to read the changelog, which I am often guilty of passing over.
 
Alpha 3 builds are now available (the new build notification can take a few hours to appear, as I'm testing with a long time-to-live cache at the moment). The main change related to the new update notification is now, when clicking on "Visit download site" on the Changelog popup you will be automatically sent to the download folder of your specific router model.

Sometime this weekend I will push a fake alpha 4 release so people can test this functionality after they've upgraded to alpha 3.

Saturday 19.00Hrs ( UK) , have not seen the new version notification and when I checked for new firmware and clicked the link I was taken to https://asuswrt.lostrealm.ca/download/ , not the folder for my router.
 
Just installed the Alpha 3. I am guessing the Beta box needs to be checked to get notices of newer alpha and the beta version, right?

Correct.
 
I like it. It almost forces you to read the changelog, which I am often guilty of passing over.

Kudos to Asus for implementing this one.

Saturday 19.00Hrs ( UK) , have not seen the new version notification and when I checked for new firmware and clicked the link I was taken to https://asuswrt.lostrealm.ca/download/ , not the folder for my router.

You have to check the "Beta" checkbox before clicking on the Check button.

I believe the current time to live of the cache was 6 or 8 hours. The CDN seems to expire the cache independently for each of their servers around the world, so while some people probably instantly got the new notification, others would have received it later.

The download link won't change until you flashed the new firmware - that link is part of the firmware, not of the update notification (Asus seems to have a - currently unused - capability of providing a download URL, but I decided not to use it, for various reasons).
 
A fake beta 9 update has just been pushed to the update server. Please test the Visit Download Site button - it should lead you to your router model's download folder on Mediafire.

(Alpha builds will point you to the global Test Builds folder, which is why I had to make it a fake beta rather than a fake alpha).

Note that you need to be already on alpha3 for this to work. Alpha2 will send you to the global download page instead.
 
Check fw update worked with pop up.
Button led me to proper web page for my router.
 
A fake beta 9 update has just been pushed to the update server. Please test the Visit Download Site button - it should lead you to your router model's download folder on Mediafire.

(Alpha builds will point you to the global Test Builds folder, which is why I had to make it a fake beta rather than a fake alpha).

Note that you need to be already on alpha3 for this to work. Alpha2 will send you to the global download page instead.

That seems to have worked. Went to the RT-AC68U Folder for me. If the beta was really there I would need go into the beta folder first, of course (I did not see an actual beta 9 file). I did not see an actual notice that a new one was available as it was probably in between checks. Reminds me.. does it create a syslog or some other indication of when the last time it checked was?
 
That seems to have worked. Went to the RT-AC68U Folder for me. If the beta was really there I would need go into the beta folder first, of course

That's something I thought about just as I tested it today - sending users to the Beta/ sub-folder might be a good idea.

(I did not see an actual beta 9 file)

There wasn't any. I only added a Beta 9 entry on the update server's manifest, and generated a changelog file there. The firmware check uses that manifest (a small text file) to determine the presence of new firmwares, it does not check for the presence of an actual zip file on the separate Mediafire server. It also means that when I release a new version, I could wait a few hours before also publishing it to the update server, in case there's something broken in the new release.

Reminds me.. does it create a syslog or some other indication of when the last time it checked was?

No. The check is currently made every 48 hours, as well as at boot time. There will be a flashing icon at the top of the webui when there's a new release available (betas/alphas do not trigger that icon). I considered generating a log entry to at least report when a new firmware was found, but it might generate a fair amount of log noise if someone only checks every few months, so for now I decided not to log it. I might change that in the future.
 
I thought I understood the thread before I posted yesterday, but perhaps not. My signature says I'm 'new around here' but though I haven't posted, I've been lurking and reading on this and other FW forums for some years. I meant only to respond to Merlin's request for input, not to initiate a privacy debate about my own reflection on the topic. I belieive I've missed where auto ID recognition and updating will take future FW updates for Merlin (and possibly Asus), or what is it that Asus may/may not do down the road? I schedule time to get by the forums monthly. The entire site provides a great deal of info and interesting feedback, but I update my routers only when it's necessary for my system, when there is specific risk, such as when SSL or OpenVPN has been patched on all models. I've bookmarked update pages, so manually locating, downloads and flashing would seem difficult to mess up, to me. I don't have any interest in allowing a router (or an OS) to perform this function for me. Up to now, few router manufacturers have attempted to push unannounced updates. Those that did, have proven disastrous at times; Ooma bricked my Ooma VoIP/router with an unannounced upgrade, which wasn't supposed to affect my newer unit. The infamous unwanted, stealth OS-push of last summer bricked an SSD, even though I'd taken pains to lock it out, and it was off-line for a week. Thankfully my Asus routers have never been affected, and I've never bricked a router or system by manually downloading/updating. Many on this forum reset their units daily and sometimes more, and also haven't lost a router, but I'm cautious. I wait a while following each release, to check other's comments on their results. I updated both Asus units after first rumors of leaks surfaced, since Asus was never known for being proactive or with providing fixes. Asus didn't use to see the need to post a hash for FW downloads on their site. I hope I haven't missed the point here, and didn't mean to go astray. Does the new notification system mean Merlin updates will now become automatic and can't be reverted, or will users face mandatory cycles, with or without opting-in or out? Will owners lose their historical, manual ability to revert, or will the ability to flash to a different 3rd party FW remain intact? I like Merlin FW and am sitting on the fence today. I stumbled into this thread last night, as I was preparing to update both routers, to take advantage of the recent fixes. I'm not particularly politically correct, but the "love it or leave it" sentiment meant something far different to me in a different era, pardon my confusion. I'd be grateful for a PM/note, to help me sort it out so, I don't limp around or drag this thread along. I'm not senile yet, just tired. Final question, will routers whose IPs are assumed by a VPN, (or in the case of multiple routers, or use of more than one VPN on a different day), cause ID headaches for Merlin and the server? I liked Interconnect's post, since I've always checked the page and model manually. Thanks for bearing with me.
 
It's ok.. but I've no flash icon

Same here. No flashing notification icon today (on alpha3) or last night (waited for it for several hours on alpha2).

But the "Check" button on alpha3 did direct me to the N66 folder.
 
Does the new notification system mean Merlin updates will now become automatic and can't be reverted, or will users face mandatory cycles, with or without opting-in or out?

I don't think Merlin's firmware will auto-install an upgrade. At most it will do is alert when an update is available and then up to you to update. In any case, you can change the setting to make it not check for firmware updates, same as turning off Windows Automatic updates.
 
RMerlin post #90
Betas and Alphas do not trigger icon.
 
Alpha 3 directed me to the correct download folder for both of my routers. Nice work, Merlin!
 
Thanks for the feedback. I'll disable the fake beta 9 report.
 
Status
Not open for further replies.

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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