Posted: Fri Feb 12, 2010 12:52 Post subject: Getting Upload only with Rflow on new router
Hi guys,
I got last week a new WRT320N on which I installed:
DD-WRT v24-sp2 (12/19/09) big - build 13493M NEWD-2 K2.6 Eko
Everything is great besides Rflow.
I'm not new with it though, I feel like I'm missing something...
Well the thing is, I'm getting only Upload report. I tried with ntop on Linux, Rflow Collector on Win32. Collector shows upload correctly, 0.000 MB in DL, and nothing in CDL.
I tried to change the interfaces (note that I reboot the router each time), but LAN & WLAN should suffice. I don't get it.
Yes I checked many times those details. Besides, I had to change the IP address on the router (Services tab) to try Rflow with several collectors. As I said: ntop under Linux, then Rflow Collector under Win32.
Each time I get the same thing: Rflow only reports the outcoming traffic for my clients. And it does it precisely, as it should!
I don't. I really don't see the incoming traffic by double-clicking one node in Rflow Collector. ...Because Rflow doesn't report the incoming traffic (I would see it in the main interface anyway).
I get the same result with ntop on a Linux computer.
When I do the same procedure with my old WRT54GL (under v23 SP2 (09/15/06) std - build 3932), I get everything, In & Out traffic.
I don't understand what you mean, i have SP2 devices, and if i edit one client with rflow i have this incoming trafic... Here is the result screen copy, do you have the same kind of result?
As I was explaining, I get only outgoing traffic:
If I click "In" in the top right-hand corner of that GUI, the "Traffic Bar" shows nothing, zero!
But don't get me wrong, there IS traffic coming in, as there has always been. I can see it when I replace my WRT320N by my old WRT54GL (older build of DD-WRT v23).
I was just passing by because I still have this *** problem, and I almost feel releaved seing that somebody else is also having that issue!
So that makes builds 13493M big and 13575M big incriminated. Maybe we should do something and tell some DD-WRT staff about that bug in case they don't know yet? So that they could try to fix it..?
Maybe we should do something and tell some DD-WRT staff about that bug in case they don't know yet? So that they could try to fix it..?
I created a bug report for it, which was closed and marked as a duplicate of a bug report that's been around for 9 months or so, so it doesn't look
likely this will be fixed imminently. Oh, and since my earlier posting I have upgraded to build 13972M, but that one has the same problem.
I have the same problem since I upgraded my 310n to 2.6 kernel. I tried builds 14929 and 14896. It is working fine with a 2.4 kernel. Anyone know how to fix this?