How are hostnames updated? e.g. manual edits of user.js or dynamically from dnsmasq.leases?
Conan
Conan - currently the former
Read tons of posts on YAMon and predecessors. Really appreciate what you did with YAMon. Amazing work. It's a quick way to narrow down who/what is using the network.
I chose DD-WRT over other firmwares partly because of YAMon.
It would be nice to have dynamic update of hostnames and integration into the DD-WRT webpages (as a MyPage?). I ended up writing awk scripts to convert dnsmasq.conf and dnsmasq.leases into user.js format. I'll post the scripts or regular expressions if they're useful to anyone.
Is Optware required by YAMon itself? Optware was mentioned in the installation instructions but I think this was more to enable USB support. The installation instructions leave the impression Optware is a YAMon requirement.
It would be nice to amend the instructions to clarify when Optware is required. This is particularly relevant for Atheros installations because Optware on Atheros a bit of a pain to do.
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=893820#893820
How are hostnames updated? e.g. manual edits of user.js or dynamically from dnsmasq.leases?
Conan
Conan - currently the former
Read tons of posts on YAMon and predecessors. Really appreciate what you did with YAMon. Amazing work. It's a quick way to narrow down who/what is using the network.
I chose DD-WRT over other firmwares partly because of YAMon.
It would be nice to have dynamic update of hostnames and integration into the DD-WRT webpages (as a MyPage?). I ended up writing awk scripts to convert dnsmasq.conf and dnsmasq.leases into user.js format. I'll post the scripts or regular expressions if they're useful to anyone.
Conan
I'd love to see those scripts and would happily incorporate them into the main script (presuming that you don't mind)
Integration with MyPage has been on my radar for a while... It's taken far longer than expected to get V2 settled down... Sigh!
Is Optware required by YAMon itself? Optware was mentioned in the installation instructions but I think this was more to enable USB support. The installation instructions leave the impression Optware is a YAMon requirement.
Conan
I'm running on a Netgear R6250 with no optware at all, and with YAMon2 installed on a USB drive, so it doesn't seem there should be any requirement there. My dd-wrt version:
Read tons of posts on YAMon and predecessors. Really appreciate what you did with YAMon. Amazing work. It's a quick way to narrow down who/what is using the network.
I chose DD-WRT over other firmwares partly because of YAMon.
It would be nice to have dynamic update of hostnames and integration into the DD-WRT webpages (as a MyPage?). I ended up writing awk scripts to convert dnsmasq.conf and dnsmasq.leases into user.js format. I'll post the scripts or regular expressions if they're useful to anyone.
Conan
I'd love to see those scripts and would happily incorporate them into the main script (presuming that you don't mind)
Integration with MyPage has been on my radar for a while... It's taken far longer than expected to get V2 settled down... Sigh!
Two awk scripts for creating user.js files from dnsmasq.conf and dnsmasq.leases are attached. The script dnsmasq.leases.awk is the most likely to be used but I statically assign IP addresses in a custom dnsmasq.conf and use dnsmasq.conf.awk.
The regular expressions are the parts probably most useful for YAMon integration because they parse dnsmasq.conf and dnsmasq.leases into regular expression match groups and can be used in any programming language like javascript to parse fields from dnsmasq.leases entries.
I would love this as an option. I've become too used to my own naming scheme now to want to change it up.
Maybe as a way to populate new devices? Then once they are in the Users.js you can change them and they are maintained?
I've something running on my router now... when a new device is detected on the network (i.e., no matching MAC address in users.js), I try to get the name from the dnsmasq.leases file (and if there is no match, I default to the generic `New Device`). It will not change any of the pre-existing entries in users.js.
I'm going to test it for a bit before putting it out
Al,
that's great news!
So if I have 4 "new device" already in my users.js will those be attempted to dnsmasq or will we have to delete those devices so they can be re-discovered for the dnsmasq process to give us a resolve attempt?
al_c wrote:
It will not change any of the pre-existing entries in users.js.
Al
_________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
Al,
that's great news!
So if I have 4 "new device" already in my users.js will those be attempted to dnsmasq or will we have to delete those devices so they can be re-discovered for the dnsmasq process to give us a resolve attempt?
al_c wrote:
It will not change any of the pre-existing entries in users.js.
Al
Now that you mention it, I suppose that I could look for new devices in users.js and try to update them as well...
But for the time being, the only way to trigger the updates is, as you suggested, to delete the entries from users.js (in /opt/YAMon2/data/). The updated file will get copied to /tmp/www /data/ within a few moments.
NB - this new feature is not available in 2.0.7. I want to make sure things are still running properly on my router before letting this out into the wild... that should be in a day or two. OK?
I've something running on my router now... when a new device is detected on the network (i.e., no matching MAC address in users.js), I try to get the name from the dnsmasq.leases file (and if there is no match, I default to the generic `New Device`). It will not change any of the pre-existing entries in users.js.
I'm going to test it for a bit before putting it out
Al
Would it be possible to amend the name update process to first update users.js from static names (nvram static_leases and dnsmasq.conf) and then update from dynamic names (dnsmasq.leases)? That would cover all the places that names would come from.
