And this presents me with a conundrum... different regular expressions required for different firmwares... how to best address that without having to manage multiple versions of the script.
Al
Perhaps we can convince Kong to add some info in the nvram for you to read.
Setting the Software Version Number with the command nvram set svn=24500, nvram commit
returns 24500 with the command nvram get svn
This would provide you and other devs a reference
for < > if then else routines to choose clib or musl
specific calls.
easypeasy ????
Dave[/quote]
A possible solution but I expect Kong will tell me to fix my regular expressions. And I agree that that is the better/best solution.
I learned something last night... the `+` meta character (used to match one or more patterns), even though it is used widely in many (Windows) regular expression libraries, is not actually in the Posix standard.
If you read back through this topic, you'll find that regex's have been problematic in the past - e.g., we found earlier that different instances of the firmware did not like just `+` but instead required `\+`... this is actually better represented using the Posix implementation `\{1,\}` so I've got through YAMon and replaced them and things seem to be running properly on my pre-24500 firmware. I'm looking for a few 24500 guinea pigs... Dave??
Posted: Thu Jul 10, 2014 0:25 Post subject: pre release of yamon 2.0.10 - fix for Kong 24500 build
al_c wrote:
I'm looking for a few 24500 guinea pigs... Dave??
Al
Here is an updated version of yamon2.sh that should fix things for those of your who are running the new Kong 24500 build. It is running happily on my pre-24500 router so I hope/expect that it'll run on all other firmware versions as well (famous last words...)
NB - This is not a full package - the zip file contains just yamon2.sh. New users should download the full package from http://www.dd-wrt.com/phpBB2/viewtopic.php?t=259806 and then replace that yamon2.sh with this one.
You will have to
1. stop the current instance of yamon if it is running (`/opt/YAMon2/Setup/yamon2.sh --stop`)
2. copy the contents of this zip file to `/opt/YAMon2/Setup/`
3. if you are running on the 24500 firmware, delete the hourly usage file for today in `/opt/YAMon2/data` (you're not losing anything as it does not contain meaningful results)
4. restart the script (`/opt/YAMon2/Setup/yamon2.sh`)
The main update in this version is the replacement of `bad` regular expressions with Posix friendly versions.
I have added a few new features in this build... in the hour usage file, the `pnd(...)` lines include an uptime parameter which allows me better calculate usage at the router (i.e., it allows me to differentiate between restarts and rollovers in the data I get from the router). I also include the server uptime in the hourly usage file.
As usual, if you notice any issues or would like to see a feature added or modified, don't hesitate to contact me.
Posted: Thu Jul 10, 2014 18:40 Post subject: Running on 24500M
Al,
I wanted to report back that I've got YAMon2 installed on Kong's 24500M build. I'm waiting for a few days to get some data captured and will let you know if I see any issues.
I have a question for you, or someone else that may know. I was unable to get the files to show up in WinSCP. I ended up doing a chmod +x via PuTTY. Do you know what I might be doing wrong with WinSCP? It connects with a user I setup in the webif, but not with my root account--although I forgot to try my webif account--but I am not able to see any files. _________________ R7000 Nighthawk - DD-WRT v3.0-r50308
R7000 Nighthawk - DD-WRT v3.0-r50308
~~~~~~~~~~Dismantled for learning opportunities~~~~~~~~~~
WRT54Gv2
WRT54Gv8.2
~~~~~~~~~~Other Settings~~~~~~~~~
https://nextdns.io/?from=2d3sq39x https://pi-hole.net/ https://github.com/DNSCrypt/dnscrypt-proxy
Posted: Fri Jul 11, 2014 4:39 Post subject: Re: Running on 24500M
HalfBit wrote:
Al,
I have a question for you, or someone else that may know. I was unable to get the files to show up in WinSCP. I ended up doing a chmod +x via PuTTY. Do you know what I might be doing wrong with WinSCP? It connects with a user I setup in the webif, but not with my root account--although I forgot to try my webif account--but I am not able to see any files.
You should login with Winscp as root so you'll have rwx permissions to change properties.
Posted: Fri Jul 11, 2014 14:31 Post subject: Re: Running on 24500M
ddaniel51 wrote:
HalfBit wrote:
Al,
I have a question for you, or someone else that may know. I was unable to get the files to show up in WinSCP. I ended up doing a chmod +x via PuTTY. Do you know what I might be doing wrong with WinSCP? It connects with a user I setup in the webif, but not with my root account--although I forgot to try my webif account--but I am not able to see any files.
You should login with Winscp as root so you'll have rwx permissions to change properties.
Dave
I've tried:
- Changing settings in WinSCP to FTP, SCP, SFTP. Result: only FTP gets the connection which is obvious as I understand ports but thought maybe something was enabled in the firmware internally.
- Changing settings in WinSCP for FTP encryption. Result: The router doesn't understand the encryption.
- Logging in with root user with webif password. Result: Access denied.
- Logging in with admin user with webif password. Result: Access denied.
- Adding root user with webif password under Services>NAS>File Sharing>Users. Result: Not able to view files/folders.
- Adding admin user with webif password under Services>NAS>File Sharing>Users. Result: Not able to view files/folders.
- Creating a separate ftp user from root/admin with a different password under Services>NAS>File Sharing>Users. Result: Not able to view files/folders.
I know I'm just not doing something simple right. How do I give root permissions to FTP? _________________ R7000 Nighthawk - DD-WRT v3.0-r50308
R7000 Nighthawk - DD-WRT v3.0-r50308
~~~~~~~~~~Dismantled for learning opportunities~~~~~~~~~~
WRT54Gv2
WRT54Gv8.2
~~~~~~~~~~Other Settings~~~~~~~~~
https://nextdns.io/?from=2d3sq39x https://pi-hole.net/ https://github.com/DNSCrypt/dnscrypt-proxy