Listing comments
| Post | Author | Url | Body | ||||
|---|---|---|---|---|---|---|---|
| Monitoring OpenWRT with NTOP | Simon | shreddedglory@gmail.com | http://shine.eu.org/ | Thanks for the tip! I also set up fprobe on my OpenWRT-running router and feed my HTOP-running laptop, and it works great. HTOP isn't as real-time as I'd like (since it has a web-based interface that has to reload when it updates), but for larger networks it could prove very useful for diagnosing problems. As a side note, my interface was called 'br-lan', but this probably depends on the version of the OpenWRT firmware and the router in question, since most documentation also calls it br0. | Show | Edit | Destroy |
| Monitoring OpenWRT with NTOP | hardly | ogredeschnique@hotmail.com | Thanks for this info. One thing though. How do I init scripts? (See what I did there?) Also haha HTOP. That's ok. I am sometimes incapable of typing i's, favoring heavily instead the o key. | Show | Edit | Destroy | |
| Monitoring OpenWRT with NTOP | Steven | gthugdeluxe@aol.com | I believe he is referring to the resource monitoring program, htop. You can find information here: http://htop.sourceforge.net/ But at least you were kindly pointing out the falsely assumed typo, instead of being a jerk like a lot of the internet-identities. Also -- To the Author -- Wonderful information here. Your article is very high when google searching "openwrt ntop" and provides a much more practical method to using ntop with an embedded system rather than trying to compile the ntop binaries themselves and run locally. While I'm sure one could use CIFS to accomplish this, it is still a method that provides results after about 3 minutes of work! Thanks again. | Show | Edit | Destroy |
New comment