iptraffic feature request

Discussion in 'Tomato Firmware' started by rs232, Mar 22, 2012.

  1. rs232

    rs232 Network Guru Member

    Hi all,
    I was wondering... how difficult/helpful would it be to be able to have all the devices in the same ip traffic chart. This would give us a quick instant check on who/what's generating traffic.

    As it is now I need to click every tab (device) and check individually.

  2. rspierz

    rspierz Networkin' Nut Member

  3. Toastman

    Toastman Super Moderator Staff Member Member

    Hmmm. Here that would mean 170 people on one chart. Hell, what processing power would be needed? How would you see anyone on the graph? My version is intended to work with 250 users, and anything I add should support that many (The PPTP server doesn't though :eek: ).
  4. Planiwa

    Planiwa Network Guru Member

    IP Traffic Daily will easily show active "trafficers". No need to "click every tab". Just use the two windows in conjunction.
  5. rs232

    rs232 Network Guru Member

    Fair enough, with many clients I totally agree. How about a top-n? Where e.g. N= 5?
    I mean AFAIK the IP data is there collected, and I would just need to know instantly who's generating traffic. As it is now I use the QoS chart + QoS details, but it's a pain in the neck, it takes time and it's not that accurate.
    The daily traffic woul do if you monitor for an extended period of time. My point refers to instant monitoring. Sometime you make a change to your network and you need to know how the WAN trafic is affected.

    Thanks :)
  6. teaman

    teaman LI Guru Member

    Well... the IP Traffic Real-Time and Last 24h pages were based on their counterparts inside the Bandwidth menu - in fact, pretty much everything IP Traffic-related on the webUI has been built on top of the existing features/functionality of similar Bandwidth-related pages... And I'm afraid those weren't really planned/designed/thought to handle lots of items (interfaces/devices) simultaneously :( (although there's been already some patching/fixing/improving towards mitigating some of that)

    In fact, one of the things that had been added to both IP Traffic Real-Time and Last 24h graphs/pages as per feedback/request from Mr. Toastman has been... the ability to show/hide some of the devices/addresses available on the list of tabs above those graphs (to be selected/picked/chosen on those graphs). By allowing the user to do some filtering and by trying to make any changes consistent across different pages at runtime, we were thinking about improving usability as well as trying to reduce clutter on the web interface ;)

    A few months ago I started playing with bringing some pie charts to IP Traffic, using the QoS stuff... but since that was mostly about 'seeing how such thing would look at runtime' and was pretty much a bunch of quick'n'dirty hacks so I could get it working, I eventually realized such thing would require some major rethinking in order to be actually useful, so it got pulled out/ditched just a few weeks later :( (it can be found in the git log/history, though)

    On the other hand, may I suggest perhaps taking a look at the IP Traffic -> Transfer Rates/Details page? If I remember properly, that particular page was probably the very first thing I wrote, even before I even had thought about cstats/history tracking and/or any of the other IPtraffic-related stuff:

    This one can be quite handy , since it was thought about being some sort of runtime/snaptshot, containing as much information as possible about what was going on through the router from/to each known/monitored device.

    Last but not least - I must confess there are not much of real plans regarding changes in any of those pages right at this moment... but don't loose all hope just yet! Those seem to be valid points and your suggestions were noted. So, it might be actually possible we do get to see some improvements in the IP Traffic web UI :) On the other hand... please keep in mind that in order to actually get these rolling... it might require some major rethinking/reworking on the code in order to make those happen - so don't hold your breath, 'cause it may take a while until we get there :/
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice