View Single Post
  #23 (permalink)  
Old 05-27-2008, 04:12 PM
seaweedsl
Guest
 
Posts: n/a
Default Re: DD-WRT & rflow collector

On May 26, 2:23 pm, Jeff Liebermann <je...@cruzio.com> wrote:
> DD-WRT v24 final release arrived last week. I've installed it on
> several non-critical machines. It's working just fine,...


Great news. I guess it's time to update ours.

> While you're at it, here's another mystery. Go to "Services" tab and
> scroll down to the very bottom of the list. There's something called
> "WAN Traffic Counter - ttraff daemon". I enabled it and tried to
> decode it's purpose, but failed. The source code is interesting:
> <http://svn.dd-wrt.com:8000/dd-wrt/browser/src/router/rc/ttraff.c?rev=...>
> and says "used for collecting and storing WAN traffic info to nvram".
> Ok, so where do I find it and how do I use the collected data?


I'm not even guessing. I can see some numbers moving for each user
connected. For now, that's my info:
Who's online, and how their numbers compare to others.

> Well, I hate to admit a small failure, but I was sympathetic (and
> bored) yesterday. So, I downloaded the latest MRTG and decided to
> scribble a web page detailing what it takes to monitor a DD-WRT based
> router.


Fantastic ! This could really help.
>
> The first thing I discovered is that the MRTG Windoze install and
> setup instructions have a few major errors. The next thing I
> discovered is that I had no easy way to generate a dynamic list of MAC
> addresses so that new graphs could be created on the fly. I think I
> can do that with MACupd or more crudely with arp -a or a simple Perl
> script. Within about an hour, I discovered that I had a major project
> on my hands and gave up for now. I hate programming...
>


OK, so at least that verifies I'm not a total idiot - it is hard.

> I tried the Windoze (demo) version of NTOP recently. It was even more
> complicated to setup than before. I did manage to configure Netflow
> (2055) but couldn't get NTOP to display any data. It was also
> irritating to find that I had to configure an ethernet interface for
> data sniffing, even though I wasn't using it.


That was my experience. Also, it clashes with Rflow and messes it up
as well.


Thanks Jeff. This affirms the value of Rflow. Not only is it the
only one that works readily, but also, if more people use it, maybe
somebody will take the initiative and improve it.

Steve

Reply With Quote