Hey, just installed yamon a couple of days ago, and I think its great.
I've only had one problem, and it seems like its similar to something that happened earlier this month. When geolocating IP addresses, most of them work, but when for some of them, when I click on them it turns all of the ip addresses that haven't been geolocated into "Rackspace Cloud Servers." Then when the live data updates, all IP addresses change into "Rackspace Cloud Servers" even the ones that where identified otherwise before.
I'm not sure exactly what this is, but I think it might have to do with twitch.tv, since it becomes more common when watching twitch streams.
Somehow a bad CIDR entry has gotten into the database (again).
Ever since YAMon3.4, I had to turn off the _includeIPv6 because I was getting many entries of "incomplete" placed into my users.js file.
YAMon has the command near line 170 of:
_getIP6List="$_path2ip -6 neigh | grep -Evi \"$_local_ip6\" | cut -d' ' -f1,5 | tr 'A-Z' 'a-z' $sortStr"
I ran only ip -6 neigh and got:
:/opt/YAMon3# ip -6 neigh
2601:600:997f:d124:7a4b:87ff:fe7b:ea3 dev br0 lladdr 78:4b:87:7b:0e:a3 STALE
fe80::eab4:c8ff:fe7f:30a9 dev br0 lladdr
fe80::287:31ff:fe90:d822 dev eth0 lladdr 00:87:31:90:d8:22 router REACHABLE
2601:600:997f:d124:e50f:7e34:b369:376e dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
2601:600:997f:d124:7165:4609:2a2:a5fa dev br0 FAILED
2601:600:997f:d124:a0ad:8b18:1357:340e dev br0 FAILED
2601:600:997f:d124:3dcd:20a8:82c1:c1e3 dev br0 FAILED
2601:600:997f:d124:70c0:31e2:1de1:45dd dev br0 lladdr 10:ae:60:82:41:fd STALE
fe80::349c:5b35:e50:637 dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
Using ip -6 neigh | cut -d' ' -f1,5 | tr 'A-Z' 'a-z'
I would get:
2601:600:997f:d124:18f9:343c:dcdf:d554 failed
fe80::d5d:a39b:1751:f640 bc:ae:c5:c0:ee:55
fe80::7a4b:87ff:fe7b:ea3 failed
fe80::12ae:60ff:fe82:41fd 10:ae:60:82:41:fd
fe80::2ac6:8eff:fe36:755c 28:c6:8e:36:75:5c
2601:600:997f:d124:dc76:a25e:1429:5ba9 failed
So my question is...Are the entries with "failed" causing a problem?
Ever since YAMon3.4, I had to turn off the _includeIPv6 because I was getting many entries of "incomplete" placed into my users.js file.
YAMon has the command near line 170 of:
_getIP6List="$_path2ip -6 neigh | grep -Evi \"$_local_ip6\" | cut -d' ' -f1,5 | tr 'A-Z' 'a-z' $sortStr"
I ran only ip -6 neigh and got:
:/opt/YAMon3# ip -6 neigh
2601:600:997f:d124:7a4b:87ff:fe7b:ea3 dev br0 lladdr 78:4b:87:7b:0e:a3 STALE
fe80::eab4:c8ff:fe7f:30a9 dev br0 lladdr
fe80::287:31ff:fe90:d822 dev eth0 lladdr 00:87:31:90:d8:22 router REACHABLE
2601:600:997f:d124:e50f:7e34:b369:376e dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
2601:600:997f:d124:7165:4609:2a2:a5fa dev br0 FAILED
2601:600:997f:d124:a0ad:8b18:1357:340e dev br0 FAILED
2601:600:997f:d124:3dcd:20a8:82c1:c1e3 dev br0 FAILED
2601:600:997f:d124:70c0:31e2:1de1:45dd dev br0 lladdr 10:ae:60:82:41:fd STALE
fe80::349c:5b35:e50:637 dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
Using ip -6 neigh | cut -d' ' -f1,5 | tr 'A-Z' 'a-z'
I would get:
2601:600:997f:d124:18f9:343c:dcdf:d554 failed
fe80::d5d:a39b:1751:f640 bc:ae:c5:c0:ee:55
fe80::7a4b:87ff:fe7b:ea3 failed
fe80::12ae:60ff:fe82:41fd 10:ae:60:82:41:fd
fe80::2ac6:8eff:fe36:755c 28:c6:8e:36:75:5c
2601:600:997f:d124:dc76:a25e:1429:5ba9 failed
So my question is...Are the entries with "failed" causing a problem?
Which are getting added as incomplete... the fe80.* entries or the 2601.*'s? If the former, make sure that that prefix exists in `_local_ip6` in your config.file.
Why is this happening? A while ago, I noticed that the incomplete and/or failed IP addresses could occasionally have traffic so rather than simply dropping those bits, I changed the behaviour to add the incomplete mac's. Do you ever see any traffic for those entries?
I could (relatively easily) add a switch to ignore them again.
Ever since YAMon3.4, I had to turn off the _includeIPv6 because I was getting many entries of "incomplete" placed into my users.js file.
YAMon has the command near line 170 of:
_getIP6List="$_path2ip -6 neigh | grep -Evi \"$_local_ip6\" | cut -d' ' -f1,5 | tr 'A-Z' 'a-z' $sortStr"
I ran only ip -6 neigh and got:
:/opt/YAMon3# ip -6 neigh
2601:600:997f:d124:7a4b:87ff:fe7b:ea3 dev br0 lladdr 78:4b:87:7b:0e:a3 STALE
fe80::eab4:c8ff:fe7f:30a9 dev br0 lladdr
fe80::287:31ff:fe90:d822 dev eth0 lladdr 00:87:31:90:d8:22 router REACHABLE
2601:600:997f:d124:e50f:7e34:b369:376e dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
2601:600:997f:d124:7165:4609:2a2:a5fa dev br0 FAILED
2601:600:997f:d124:a0ad:8b18:1357:340e dev br0 FAILED
2601:600:997f:d124:3dcd:20a8:82c1:c1e3 dev br0 FAILED
2601:600:997f:d124:70c0:31e2:1de1:45dd dev br0 lladdr 10:ae:60:82:41:fd STALE
fe80::349c:5b35:e50:637 dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
Using ip -6 neigh | cut -d' ' -f1,5 | tr 'A-Z' 'a-z'
I would get:
2601:600:997f:d124:18f9:343c:dcdf:d554 failed
fe80::d5d:a39b:1751:f640 bc:ae:c5:c0:ee:55
fe80::7a4b:87ff:fe7b:ea3 failed
fe80::12ae:60ff:fe82:41fd 10:ae:60:82:41:fd
fe80::2ac6:8eff:fe36:755c 28:c6:8e:36:75:5c
2601:600:997f:d124:dc76:a25e:1429:5ba9 failed
So my question is...Are the entries with "failed" causing a problem?
Which are getting added as incomplete... the fe80.* entries or the 2601.*'s? If the former, make sure that that prefix exists in `_local_ip6` in your config.file.
Why is this happening? A while ago, I noticed that the incomplete and/or failed IP addresses could occasionally have traffic so rather than simply dropping those bits, I changed the behaviour to add the incomplete mac's. Do you ever see any traffic for those entries?
I could (relatively easily) add a switch to ignore them again.
Thoughts?
I did ip -6 neigh | grep FAILED and the results was mostly 2601. I got one for fe80 that is my dev br0
fe80::7a4b:87ff:fe7b:ea3 dev br0 FAILED
2601:600:997f:d124:a42f:717a:aadd:17a0 dev br0 FAILED
My config.file has
_local_ip6='fe80:,2601:'
I would have to set the _includeIPv6=1 and see if there is any traffic. From my last attempts I saw very little traffic. Perhaps a switch would be of use. Anyone else think so? _________________ Netgear R7800: DD-WRT v3.0-r47822 std (12/09/21)
Linksys wrt1900acsV2: DD-WRT v3.0-r47822 std (12/09/21)
Joined: 14 Nov 2017 Posts: 30 Location: Scania, Sweden
Posted: Sun Aug 12, 2018 16:19 Post subject: Yamon stopping
Yamon stops running from time to time. It seems there it stops running by the end of the month regularly.
Is anyone else having this problem?
I am running Linksys WRT3200 with DD-WRT r36079 and Yamon 3.4.5 _________________ _____________________________________________________
Linksys WRT3200ACM: DD-WRT r41418
Linksys LGS116P Switch
Linksys EA6300: Original firmware, as bridge
Ubiqity Unifi AP AC Lite
Ubiqity Unifi AP AC LR
Ubiqity Unifi AP AC Pro
I had a problem recently when Yamon was stopping and I remembered reading that there needs to be a blank line at the end of users.js (amongst others) and I had somehow removed this when editing. I put the blank line in and no problem since.
heya, I just updated from 3.3.6 to 3.4.5 and now i am getting an error
"users_created is not defined... there is likely an error in your users.js"
the users.js looks fine to me. i also get a message in the putty window about my router not having NTP on, which is incorrect. It is on, i double checked. Not sure if that could be related.
after the not defined error, the text on screen says
"Loading...
Settings from database...
Devices from data/users.js
Monthly data for 2018-08
Could not open the monthly data file?!?"
and then all tabs load, but with blank data.
Hoping this is a simple fix, i most likely messed something up somewhere.
[EDIT]
Well, i tried turning the router off and back on again. And magically everything started working again. I guess issue solved? Maybe could list that as a troubleshooting step somewhere for this issue. Glad to be able to use this wonderful resource again! ;D
I had a problem recently when Yamon was stopping and I remembered reading that there needs to be a blank line at the end of users.js (amongst others) and I had somehow removed this when editing. I put the blank line in and no problem since.
I have a really vague recollection of that as well... but no idea why it might cause/resolve problems.
Thanks for pointing this out... it might help someone else.
Posted: Mon Aug 13, 2018 2:03 Post subject: Re: Yamon stopping
7kt_ql wrote:
Yamon stops running from time to time. It seems there it stops running by the end of the month regularly.
Is anyone else having this problem?
I am running Linksys WRT3200 with DD-WRT r36079 and Yamon 3.4.5
Hmmm... that is odd. Do you have logging turned on? Can you set loglevel=0 and let things run again... then send me the log if/when it occurs again. Please send it to questions@usage-monitoring.com
(do not post logs to the forum)
NB - the logs could get big so make sure you have ample free space on your usb drive (or clear out the log directory on a regular basis).
heya, I just updated from 3.3.6 to 3.4.5 and now i am getting an error
"users_created is not defined... there is likely an error in your users.js"
the users.js looks fine to me. i also get a message in the putty window about my router not having NTP on, which is incorrect. It is on, i double checked. Not sure if that could be related.
after the not defined error, the text on screen says
"Loading...
Settings from database...
Devices from data/users.js
Monthly data for 2018-08
Could not open the monthly data file?!?"
and then all tabs load, but with blank data.
Hoping this is a simple fix, i most likely messed something up somewhere.
[EDIT]
Well, i tried turning the router off and back on again. And magically everything started working again. I guess issue solved? Maybe could list that as a troubleshooting step somewhere for this issue. Glad to be able to use this wonderful resource again! ;D
I *will* add that to the troubleshooting tips... thanks for the update/suggestion.
I appears to me that there are two bugs
1. the NTP warning
2. symlinks not being updated properly when you re-run setup
(#1 should have no bearing on #2)
Ever since YAMon3.4, I had to turn off the _includeIPv6 because I was getting many entries of "incomplete" placed into my users.js file.
YAMon has the command near line 170 of:
_getIP6List="$_path2ip -6 neigh | grep -Evi \"$_local_ip6\" | cut -d' ' -f1,5 | tr 'A-Z' 'a-z' $sortStr"
I ran only ip -6 neigh and got:
:/opt/YAMon3# ip -6 neigh
2601:600:997f:d124:7a4b:87ff:fe7b:ea3 dev br0 lladdr 78:4b:87:7b:0e:a3 STALE
fe80::eab4:c8ff:fe7f:30a9 dev br0 lladdr
fe80::287:31ff:fe90:d822 dev eth0 lladdr 00:87:31:90:d8:22 router REACHABLE
2601:600:997f:d124:e50f:7e34:b369:376e dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
2601:600:997f:d124:7165:4609:2a2:a5fa dev br0 FAILED
2601:600:997f:d124:a0ad:8b18:1357:340e dev br0 FAILED
2601:600:997f:d124:3dcd:20a8:82c1:c1e3 dev br0 FAILED
2601:600:997f:d124:70c0:31e2:1de1:45dd dev br0 lladdr 10:ae:60:82:41:fd STALE
fe80::349c:5b35:e50:637 dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
Using ip -6 neigh | cut -d' ' -f1,5 | tr 'A-Z' 'a-z'
I would get:
2601:600:997f:d124:18f9:343c:dcdf:d554 failed
fe80::d5d:a39b:1751:f640 bc:ae:c5:c0:ee:55
fe80::7a4b:87ff:fe7b:ea3 failed
fe80::12ae:60ff:fe82:41fd 10:ae:60:82:41:fd
fe80::2ac6:8eff:fe36:755c 28:c6:8e:36:75:5c
2601:600:997f:d124:dc76:a25e:1429:5ba9 failed
So my question is...Are the entries with "failed" causing a problem?
Which are getting added as incomplete... the fe80.* entries or the 2601.*'s? If the former, make sure that that prefix exists in `_local_ip6` in your config.file.
Why is this happening? A while ago, I noticed that the incomplete and/or failed IP addresses could occasionally have traffic so rather than simply dropping those bits, I changed the behaviour to add the incomplete mac's. Do you ever see any traffic for those entries?
I could (relatively easily) add a switch to ignore them again.
Thoughts?
I did ip -6 neigh | grep FAILED and the results was mostly 2601. I got one for fe80 that is my dev br0
fe80::7a4b:87ff:fe7b:ea3 dev br0 FAILED
2601:600:997f:d124:a42f:717a:aadd:17a0 dev br0 FAILED
My config.file has
_local_ip6='fe80:,2601:'
I would have to set the _includeIPv6=1 and see if there is any traffic. From my last attempts I saw very little traffic. Perhaps a switch would be of use. Anyone else think so?
Ok...I now know what the problem is... According to the folks @ busybox, dd-wrt includes a busybox binary which was built without 'CONFIG_FEATURE_IP_NEIGH=y'.
Quote:
one with that option enabled would show "neigh" in --help
of ip command:
Ever since YAMon3.4, I had to turn off the _includeIPv6 because I was getting many entries of "incomplete" placed into my users.js file.
YAMon has the command near line 170 of:
_getIP6List="$_path2ip -6 neigh | grep -Evi \"$_local_ip6\" | cut -d' ' -f1,5 | tr 'A-Z' 'a-z' $sortStr"
I ran only ip -6 neigh and got:
:/opt/YAMon3# ip -6 neigh
2601:600:997f:d124:7a4b:87ff:fe7b:ea3 dev br0 lladdr 78:4b:87:7b:0e:a3 STALE
fe80::eab4:c8ff:fe7f:30a9 dev br0 lladdr
fe80::287:31ff:fe90:d822 dev eth0 lladdr 00:87:31:90:d8:22 router REACHABLE
2601:600:997f:d124:e50f:7e34:b369:376e dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
2601:600:997f:d124:7165:4609:2a2:a5fa dev br0 FAILED
2601:600:997f:d124:a0ad:8b18:1357:340e dev br0 FAILED
2601:600:997f:d124:3dcd:20a8:82c1:c1e3 dev br0 FAILED
2601:600:997f:d124:70c0:31e2:1de1:45dd dev br0 lladdr 10:ae:60:82:41:fd STALE
fe80::349c:5b35:e50:637 dev br0 lladdr 30:5a:3a:7d:fa:43 REACHABLE
Using ip -6 neigh | cut -d' ' -f1,5 | tr 'A-Z' 'a-z'
I would get:
2601:600:997f:d124:18f9:343c:dcdf:d554 failed
fe80::d5d:a39b:1751:f640 bc:ae:c5:c0:ee:55
fe80::7a4b:87ff:fe7b:ea3 failed
fe80::12ae:60ff:fe82:41fd 10:ae:60:82:41:fd
fe80::2ac6:8eff:fe36:755c 28:c6:8e:36:75:5c
2601:600:997f:d124:dc76:a25e:1429:5ba9 failed
So my question is...Are the entries with "failed" causing a problem?
Which are getting added as incomplete... the fe80.* entries or the 2601.*'s? If the former, make sure that that prefix exists in `_local_ip6` in your config.file.
Why is this happening? A while ago, I noticed that the incomplete and/or failed IP addresses could occasionally have traffic so rather than simply dropping those bits, I changed the behaviour to add the incomplete mac's. Do you ever see any traffic for those entries?
I could (relatively easily) add a switch to ignore them again.
Thoughts?
I did ip -6 neigh | grep FAILED and the results was mostly 2601. I got one for fe80 that is my dev br0
fe80::7a4b:87ff:fe7b:ea3 dev br0 FAILED
2601:600:997f:d124:a42f:717a:aadd:17a0 dev br0 FAILED
My config.file has
_local_ip6='fe80:,2601:'
I would have to set the _includeIPv6=1 and see if there is any traffic. From my last attempts I saw very little traffic. Perhaps a switch would be of use. Anyone else think so?
Ok...I now know what the problem is... According to the folks @ busybox, dd-wrt includes a busybox binary which was built without 'CONFIG_FEATURE_IP_NEIGH=y'.
Quote:
one with that option enabled would show "neigh" in --help
of ip command:
Thanks for looking into this. I checked my router and I have BusyBox v1.27.2 (2017-12-04) in which ip --help shows nothing. _________________ Netgear R7800: DD-WRT v3.0-r47822 std (12/09/21)
Linksys wrt1900acsV2: DD-WRT v3.0-r47822 std (12/09/21)
Posted: Sat Aug 18, 2018 15:29 Post subject: Strange UPD Ports Open
I hope this is the place to ask a question about what YAMon is showing me about my router. I have a Netgear R7000 router with Kong 36070M firmware installed running YAMon 3.4.5. I am monitoring the usage of the various devices on my network. My question is what would cause my router WAN, this is my router MAC address for the WAN not a device on my network, to have approximately thirty different UPD ports open to Midco Cable in Sioux Falls SD? This is not my service provider. My question is why all the open UDP ports and why to this address. Finally, is YAMon the best tool to understand why this is happening or should I be using something else?
I hope this is the place to ask a question about what YAMon is showing me about my router. I have a Netgear R7000 router with Kong 36070M firmware installed running YAMon 3.4.5. I am monitoring the usage of the various devices on my network. My question is what would cause my router WAN, this is my router MAC address for the WAN not a device on my network, to have approximately thirty different UPD ports open to Midco Cable in Sioux Falls SD? This is not my service provider. My question is why all the open UDP ports and why to this address. Finally, is YAMon the best tool to understand why this is happening or should I be using something else?
Because the data transfers are very small could these be DNS translations requests? Could I have some incorrect router setting?
