I feel stupid, where is the script located? It's name?
Can't see anything on my AC1900.
Just like all the other custom scripts, you have to create it yourself under /jffs/scripts/ .
I feel stupid, where is the script located? It's name?
Can't see anything on my AC1900.
That still does not answer my question fully.Just like all the other custom scripts, you have to create it yourself under /jffs/scripts/ .
I think I get it now, it must be called 'update-notification'.
Anyone who already has (or plans to create) an application password for AB-Solution 3 status e-mails, you can use the same one as it is the same device.alpha 4 added a new update-notification user script. Here is an example update-notification script that will email you when a new firmware is available. This script is designed for GMail, shouldn't be too hard to adapt to your own ISP's SMTP.
Code:#!/bin/sh # SMTP parameters SMTP="smtp.gmail.com" PORT="465" USERNAME="you@gmail.com" PASSWORD="gmail-password" # Mail Enveloppe FROM_NAME="Router" FROM_ADDRESS="you@gmail.com" TO_NAME="Your Name" TO_ADDRESS="you@gmail.com" ### Do not change below # Retrieve version TMPVERS=$(nvram get webs_state_info) VERS=${TMPVERS:5:3}.${TMPVERS:8:10} ROUTER_IP=$(nvram get lan_ipaddr) echo "From: \"$FROM_NAME\" <$FROM_ADDRESS>" > /tmp/mail.txt echo "To: \"$TO_NAME\" <$TO_ADDRESS>" >> /tmp/mail.txt echo "Subject: New router firmware notification" >> /tmp/mail.txt echo "" >> /tmp/mail.txt echo "New firmware version $VERS is now available for your router at $ROUTER_IP." >> /tmp/mail.txt curl --url smtps://$SMTP:$PORT \ --mail-from "$FROM_ADDRESS" --mail-rcpt "$TO_ADDRESS" \ --upload-file /tmp/mail.txt \ --ssl-reqd \ --user "$USERNAME:$PASSWORD" --insecure rm /tmp/mail.txt
Might be a good idea to define an application password to use here, since your GMail password would end up stored in the clear in that script.
tlc@RT-AC1900P:/tmp/home/root# busybox
busybox: applet not found
http://www.snbforums.com/threads/te...-380-65-alpha-builds.36508/page-4#post-300795Why on RT-AC88U in alpha 4 was removed option checkbox to checking new firmware ? And also on tools was removed...
apprently, OpenVPN Connect for iOS is not compatible with OpenVPN 2.4.x (this is what I've read on the OpenVPN forum).1.0.7 is definitely not the version of the OpenVPN client used by that applications, it has to be 2.something. Check its documentation/about to determine which version it uses.
What does "now" refer to? 380.65 alpha build installed, or a 380.64 (or earlier)?apprently, OpenVPN Connect for iOS is not compatible with OpenVPN 2.4.x (this is what I've read on the OpenVPN forum).
I can connect fine now... but I cannot use the newer options.
sorry I wasn't clear ;-)What does "now" refer to? 380.65 alpha build installed, or a 380.64 (or earlier)?
That is the case for many of the OpenVPN clients for various platforms as OpenVPN 2.4 was just recently (late December 2016) released.apprently, OpenVPN Connect for iOS is not compatible with OpenVPN 2.4.x (this is what I've read on the OpenVPN forum).
I can connect fine now... but I cannot use the newer options.
apprently, OpenVPN Connect for iOS is not compatible with OpenVPN 2.4.x (this is what I've read on the OpenVPN forum).
I can connect fine now... but I cannot use the newer options.
Almost panicked here, but now I see how it's used. Is this only doing a DNS lookup? No contact with any Microsoft servers? I apologize for the off-topic post.... it probes the host and expects Microsofts answer that the internet is alive and well...
Microsoft and apparently others probe the site for the Network Connectivity Status Indicator.Almost panicked here, but now I see how it's used. Is this only doing a DNS lookup? No contact with any Microsoft servers? I apologize for the off-topic post.
https://github.com/RMerl/asuswrt-me...74852954/release/src/router/rc/wanduck.c#L577
Thanks! This means I can upgrade as well.sorry I wasn't clear ;-)
now refers to 380.65 alpha builds... but without touching anything on my OpenVPN configuration that was already in place with 380.64 (or older)
In Alpha 4 I get:
This command works in firmware with BusyBox v1.20.2Code:tlc@RT-AC1900P:/tmp/home/root# busybox busybox: applet not found
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!