Can you add CTF (Cut Through Forwarding) to go along with SFE warnings on the manual install page please?
Effectively same operation with different descriptions depending on firmware being used.
Tnx
Dave _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
Posted: Thu Feb 22, 2018 22:33 Post subject: Re: Looking for guinea pigs to test v3.4.1
cray wrote:
Trying to run old and dev version. Scripts running but cannot get GUI to work, don't know how to configure so you can access either index.html.
Previous dev GUI would still load, after new update it hangs. If I look in /www I see a mix of 3.4 and 3.3.6 files.
root@nsagateway:/tmp/www# ls -l
lrwxrwxrwx 1 root root 19 Feb 21 04:19 css -> /opt/YAMon3/www/css
lrwxrwxrwx 1 root root 19 Feb 21 12:11 data3 -> /opt/YAMon3.4/data/
lrwxrwxrwx 1 root root 22 Feb 21 04:19 images -> /opt/YAMon3/www/images
lrwxrwxrwx 1 root root 31 Feb 21 12:11 index.html -> /opt/YAMon3.4/www/yamon3.4.html
drw-rw-r-- 2 root root 0 Feb 21 10:34 js
lrwxrwxrwx 1 root root 17 Feb 21 04:19 logs -> /opt/YAMon3/logs/
I assume this is not good and can't figure out how to option the config to create two separate trees.
I run the gui at 192.168.1.1/user/index.html. Can't figure out how to make a user2 or what the best way to do this is.
I am just about to set this up, I am going to set these vars on both the current and dev version different (may have to adjust www location for your router). I already set my current version up and it seems to work fine except for an extraneous symlink that keeps getting created.
Posted: Thu Feb 22, 2018 22:39 Post subject: Problem with dev advanced install
DEV 3.4.1 Bug Report:
Problem with dev advanced install. If I try and change some of the settings it wont take it, only seems like the defaults work on some, others I can change.
It is spamming my syslog with firewall information or something, turned logging to lvl 2 but still doing it so going to shut it down and wait for a fix.
Also I am getting some odd output when it starts and it is also repeating itself like its stuck somewhere.
Code:
Yet Another Monitor
Copyright (c) 2013-present Al Caughey
All rights reserved.
http://usage-monitoring.com
YAMon Version:: 3.4.1
**********************************************************
[: bad number
[: bad number
ln: /www/user/YAMonDev/YAMonDev: File exists
removed '/tmp/var/wwwext/YAMonDev/index.html'
removed '/tmp/var/wwwext/YAMonDev/data3'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Your reports URL: http://192.168.1.1/user/YAMonDev//index.html
~ (subject to some firmware variant oddities)
~ If your reports do not open properly, see
~ http://usage-monitoring.com/help/?t=reports-help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**********************************************************
*** `yamon3.4.1.sh` has been started
**********************************************************
To stop the script:
* run `shutdown.sh` [*RECOMMENDED*]
e.g., `shutdown.sh`
* or delete the `/tmp/YAMon3.4-running` directory
e.g., `rmdir /tmp/YAMon3.4-running`
[: bad number
ln: /www/user/YAMonDev/YAMonDev: File exists
removed '/tmp/var/wwwext/YAMonDev/index.html'
removed '/tmp/var/wwwext/YAMonDev/data3'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Your reports URL: http://192.168.1.1/user/YAMonDev//index.html
~ (subject to some firmware variant oddities)
~ If your reports do not open properly, see
~ http://usage-monitoring.com/help/?t=reports-help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2018-02-22 16_38_49-192.168.1.1 - PuTTY.png
Description:
Filesize:
18.31 KB
Viewed:
2951 Time(s)
Last edited by jtp10181 on Fri Feb 23, 2018 1:21; edited 2 times in total
Posted: Fri Feb 23, 2018 3:02 Post subject: Re: Looking for guinea pigs to test v3.4.1
jtp10181 wrote:
cray wrote:
Trying to run old and dev version. Scripts running but cannot get GUI to work, don't know how to configure so you can access either index.html.
Previous dev GUI would still load, after new update it hangs. If I look in /www I see a mix of 3.4 and 3.3.6 files.
root@nsagateway:/tmp/www# ls -l
lrwxrwxrwx 1 root root 19 Feb 21 04:19 css -> /opt/YAMon3/www/css
lrwxrwxrwx 1 root root 19 Feb 21 12:11 data3 -> /opt/YAMon3.4/data/
lrwxrwxrwx 1 root root 22 Feb 21 04:19 images -> /opt/YAMon3/www/images
lrwxrwxrwx 1 root root 31 Feb 21 12:11 index.html -> /opt/YAMon3.4/www/yamon3.4.html
drw-rw-r-- 2 root root 0 Feb 21 10:34 js
lrwxrwxrwx 1 root root 17 Feb 21 04:19 logs -> /opt/YAMon3/logs/
I assume this is not good and can't figure out how to option the config to create two separate trees.
I run the gui at 192.168.1.1/user/index.html. Can't figure out how to make a user2 or what the best way to do this is.
I am just about to set this up, I am going to set these vars on both the current and dev version different (may have to adjust www location for your router). I already set my current version up and it seems to work fine except for an extraneous symlink that keeps getting created.
In theory, you should only see _wwwPath='/tmp/var/wwwext/YAMonDev/' if your firmware is Asuswrt-Merlin, Tomato or Xwrt-Vortex... does this apply to you?!?
Posted: Fri Feb 23, 2018 3:41 Post subject: Re: Problem with dev advanced install
jtp10181 wrote:
DEV 3.4.1 Bug Report:
Problem with dev advanced install. If I try and change some of the settings it wont take it, only seems like the defaults work on some, others I can change.
It is spamming my syslog with firewall information or something, turned logging to lvl 2 but still doing it so going to shut it down and wait for a fix.
Yes to track down the `no matching mac` traffic, I added an iptables entry that sends those calls to the /var/log/messages.
With that logging entry, I've been able to tweak the iptables entries so that my `no matching mac` traffic has dropped from ~5+MB/day to maybe a few KB/day...
Has anyone else noticed this change as well? If no, please zip up your m/var/log/messages and send it to questions@usage-monitoring.com (Spoiler alert, it most cases it is internal traffic going to one of the following addresses: 255.255.255.255, 224.0.0.1, 127.0.0.1). I occasionally see a flurry of entries in the log if/when an IP address changes (which my Ooma device seems to do on a regular basis).
I meant to add a flag that turns the logging on/off but in the excitement of adding the bridge functionality, forgot to do so. You can manually kill the `spamming`
1. by removing the offending entry from the iptables chain YAMON34v4 - e.g.
iptable -D YAMON34v4 ##
(where ## is the line number of the logging rule - iptables -L YAMON34v4 --line-numbers -vnx),
or
2. by commenting out the line `eval $cmd $_tMangleOption -A "$chain" -s "$ip" -j LOG --log-prefix "YAMon: "` (somewhere around line 502 in /includes/util3.4.x.sh)
Posted: Fri Feb 23, 2018 3:43 Post subject: Re: Problem with dev advanced install
jtp10181 wrote:
DEV 3.4.1 Bug Report:
Also I am getting some odd output when it starts and it is also repeating itself like its stuck somewhere.
Code:
Yet Another Monitor
Copyright (c) 2013-present Al Caughey
All rights reserved.
http://usage-monitoring.com
YAMon Version:: 3.4.1
**********************************************************
[: bad number
[: bad number
ln: /www/user/YAMonDev/YAMonDev: File exists
removed '/tmp/var/wwwext/YAMonDev/index.html'
removed '/tmp/var/wwwext/YAMonDev/data3'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Your reports URL: http://192.168.1.1/user/YAMonDev//index.html
~ (subject to some firmware variant oddities)
~ If your reports do not open properly, see
~ http://usage-monitoring.com/help/?t=reports-help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**********************************************************
*** `yamon3.4.1.sh` has been started
**********************************************************
To stop the script:
* run `shutdown.sh` [*RECOMMENDED*]
e.g., `shutdown.sh`
* or delete the `/tmp/YAMon3.4-running` directory
e.g., `rmdir /tmp/YAMon3.4-running`
[: bad number
ln: /www/user/YAMonDev/YAMonDev: File exists
removed '/tmp/var/wwwext/YAMonDev/index.html'
removed '/tmp/var/wwwext/YAMonDev/data3'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Your reports URL: http://192.168.1.1/user/YAMonDev//index.html
~ (subject to some firmware variant oddities)
~ If your reports do not open properly, see
~ http://usage-monitoring.com/help/?t=reports-help
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To help track down the `[: bad number` errors, please set
_log2file='2'
_loglevel='0'
_scrlevel='1'
Then run restart.sh again
_log2file='2' will cause the logging messages to go to the screen and the log file
_scrlevel='1' will send only `send2log` messages of level 1 or higher to the screen but all messages of level 0 or higher will go to the log
Then find the `[: bad number` in the output on the screen... time stamps of the calls on the screen will help track down where the offending code occurs in the logs.
Can you add CTF (Cut Through Forwarding) to go along with SFE warnings on the manual install page please?
Effectively same operation with different descriptions depending on firmware being used.
Tnx
Dave
Dave - definitely yes... I've not seen CTF in DD-WRT so far... is this a new addition in the admin GUI? (I can't find it in my GUI... but I haven't updated for a couple of weeks/months now).
There is no nvram entry for CTF either... can you point me in the right direction?
CTF was an earlier version of SFE that didn't last too long but, is still around.
On another note:
/opt/data is my data path and /opt/logs is logs in config.file.
h2m.sh converts that to /opt/YAMon3//opt/data and /opt/YAMon3//opt/logs which doesn't work too well.
3.4.1 isn't writing daily results to the mac_data.js
which prompted the use of h2m and it's quirks. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
CTF was an earlier version of SFE that didn't last too long but, is still around.
On another note:
/opt/data is my data path and /opt/logs is logs in config.file.
h2m.sh converts that to /opt/YAMon3//opt/data and /opt/YAMon3//opt/logs which doesn't work too well.
3.4.1 isn't writing daily results to the mac_data.js
which prompted the use of h2m and it's quirks.
I have to confess to an embarassing `doh!` mistake in 3.4.1...
The script that aggregates the hourly data into the monthly file (/includes/hourly2monthly.sh) does not actually calculate the daily device totals . To speed up things while testing other new features, I commented out that function call and then forgot to uncomment it before uploading the the server.
You can update to v3.4.2 (by running `/opt/install.sh dev` again) or uncomment line ~#449 in /includes/hourly2monthly.sh:
#eval "$tallyHourlyData"
(just delete the # at the start of the line)
To fill-in the gaps in your monthly file, run /opt/YAMon3/h2m.sh and follow the prompts.
_logfilename-->/opt/YAMon3//opt/logs/h2m.log
_configFile-->/opt/YAMon3/config.file
touch: /opt/YAMon3//opt/logs/h2m.log: No such file or directory
./h2m.sh: line 48: can't create /opt/YAMon3//opt/logs/h2m.log: nonexistent directory
16:54:48 1 Log file: `/opt/YAMon3//opt/logs/h2m.log`.
./h2m.sh: line 49: can't create /opt/YAMon3//opt/logs/h2m.log: nonexistent directory
16:54:48 1 Loading baseline settings from `/opt/YAMon3/config.file`. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
_logfilename-->/opt/YAMon3//opt/logs/h2m.log
_configFile-->/opt/YAMon3/config.file
touch: /opt/YAMon3//opt/logs/h2m.log: No such file or directory
./h2m.sh: line 48: can't create /opt/YAMon3//opt/logs/h2m.log: nonexistent directory
16:54:48 1 Log file: `/opt/YAMon3//opt/logs/h2m.log`.
./h2m.sh: line 49: can't create /opt/YAMon3//opt/logs/h2m.log: nonexistent directory
16:54:48 1 Loading baseline settings from `/opt/YAMon3/config.file`.
If you change the h2m.sh around line 41 where it sets the _logfilename to the following code it should work. It currently is not handling absolute paths correctly.
Code:
if [ "${_logDir:0:1}" == "/" ] ; then
_logfilename="$_logDir"'h2m.log'
else
_logfilename="${d_baseDir}/$_logDir"'h2m.log'
fi
The glc.sh has this same issue. I am thinking there should be a global in maybe the defaults.sh that sets the absolute path for logs/ and data/ since those both support either absolute or relative paths in the settings. But the above trick will fix it for now.
