Posted: Mon Mar 20, 2017 21:39 Post subject: unknown mac
Things have settled nicely for me now on 3.2.5 with the manual append fix for the double zeros lines. After almost a full day running, the unknown Mac device percentage has settled down to less than one percent now (it used to indicate 100, all traffic was initially being caught by its location in the chain). The tops of the bars do indeed also now precisely align with the "data at router" line.
I also like the WAN Mac and LAN Mac auto entries in the device tab table (I assume those are also new - those previously kept showing up as unknowns for me, even when I tried to force describe them with custom device entries).
Posted: Tue Mar 21, 2017 5:13 Post subject: I just posted an update to install.sh
This update only changes `install.sh` and `compare.sh`... if your installation is currently running properly, there is no pressing need to update things right now.
`install.sh` now calls `compare.sh` and halts setup if the md5 signature of one or more files on your router does not match the value on the server. This will hopefully at least partially address the incomplete download issues that some users have reported.
Ed - The symlinks in /tmp/www seem to be wrong. Delete them and then restart the script.
Al
Al - deleted all in /tmp/www and restarted the script.
SymLinks got added during restart but no joy running the report. Using 192.168.1.1/user/index.html as that seems to be the only html file (symlink) in /tmp/www.
I get a blank page, no error. Data collection seems to be running OK, based on the data files being updated regularly.
Ed - The symlinks in /tmp/www seem to be wrong. Delete them and then restart the script.
Al
Al - deleted all in /tmp/www and restarted the script.
SymLinks got added during restart but no joy running the report. Using 192.168.1.1/user/index.html as that seems to be the only html file (symlink) in /tmp/www.
I get a blank page, no error. Data collection seems to be running OK, based on the data files being updated regularly.
Hmmmm....
I had the same problem during the install. The symlinks are all local to /tmp/www but need to be pointed to /opt/YAMon3/www. I had to remove the links from /tmp/www and re-link them manually. Unfortunately it has to be done everytime the router restarts. I had assumed it was something I did wrong during the installation process (probably was).
Al with this new version I'm unable to reboot the router without pulling the physical plug because I'm getting this:
/opt/YAMon3/shutdown.sh: line 64: did not kill process: 21103 ?!? try rebooting your router: not found
Any idea what might be causing this?
What is causing it? A crappy software developer (aka me).
I made some changes to shutdown.sh that should prevent the endless loop... I've seen what you reported once... a yamon process but a `kill pid` does not actually get rid of it.
Shutdown now better detects this oddball situation. Rerun install.sh to get the latest files.
Posted: Wed Mar 22, 2017 13:13 Post subject: Re: YAMon for Access Point
[quote="artyddwrt"][quote="bilkain"]Hi, Al,
Not sure if you missed my question or asked a dumb question, but just one to repost the below:
Thanks for your help.
[quote="bilkain"]Hello,
I know others has this problem to but is there anyway to get YAMon to work with ddwrt routers that are set up as access point? I want to be able to monitor all traffic from the Access Point router.
It seems like the only way for YAMon to detect and monitor my devices is if I'm logged into my dd-wrt router (browser interface) from that specific device, AND keep that devices logged in. Once I log out of dd-wrt or close the browser, YAMon will not be able to detect/monitor that device. Also, DDWRT> Status > LAN > active clients would only show that devices if I'm logged into DDWRT through the browser. Other than that, all the devices show up in the Wireless Client.
I think ddwrt needs to be acting as both DHCP server and gateway in order for Yamon to monitor the LAN segment/subnet. At the risk of giving you erroneous advice, you might need to set-up ddwrt as a separate subnet router/gateway (as opposed to an access-point) for the particular LAN segment you are trying to monitor with Yamon.
As far as needing to be logged into the ddwrt web interface from a device in order for that device to be monitored by Yamon, that certainly sounds odd and I have never needed to do that. Perhaps it has something to do with the fact that your ddwrt is set-up as an access point (eg: maybe it is the only time your ddwrt "sees" any IP traffic because in all other cases it is acting like a switch). What happens if you "ping" your ddwrt access-point IP address continuously from different devices, simultaneously? Does that also cause Yamon to become aware of those devices?
.[/quote]
Hi, artyddwrt. Thank you for your help. I can't seem to do much so I guess i'll just use desktop based software. Thanks again for your help.
Posted: Wed Mar 22, 2017 22:37 Post subject: Problems installing YAMon3 on shibby tomato
Hi Al,
I've been using yamon for a while on DD-wrt with no problems. Recently, I switched to tomato firmware for the bandwidth limiting option and robust qos. On tomato, yamon is installing with errors, and the reports page (192.168.1.1/user/index.html) is coming up blank even though yamon is running.
My tomato build mounts the flash disk to /mnt/sda1. I set the router to bind it to /opt (mount -o bind /mnt/sda1 /opt). I get the errors whether I bind to /opt or not.
A screenshot of the errors is attached. I have very little experience with linux, so please excuse any ignorance on my part.
