iftop-users November 2013

iftop-users@domain

4 participants
3 discussions

[Iftop-users] ancient text output patch ported to latest version
by Roman Hoog Antink 01 Jan '14

01 Jan '14

Hi there [reposted with compressed attachment so no moderation needed] Back in 2007 Patrik Bless, a former colleague, wrote the attached patch, which was never committed to the repo, because his request got stuck in the moderated forum. The patch adds a text output feature, allowing machine parsing of output or redirecting it to a file, as requested in this mailing list lately by Shannon Rodrigues. http://lists.beasts.org/pipermail/iftop-users/2012-September/000369.html Please consider adding it before version 1.0 comes out. Can someone explain, why the CVS repo has no tags for the 0.18 and 0.19 releases? Kind regards, Roman -- Roman Hoog Antink Dipl. Ing. ETH Senior Security Engineer Open Systems AG Räffelstrasse 29 CH-8045 Zürich t: +41 44 455 74 00 f: +41 44 455 74 01 rha(a)open.ch http://www.open.ch

3 5

[Iftop-users] CPU use bug?
by Alex Page 20 Nov '13

20 Nov '13

Hello, I am seeing strange behavior recently in iftop on Ubuntu (x64, 12.04 and 13.10). With Port Display disabled, iftop simply uses more CPU than normal (say, 20% instead of a negligible amount). Then, when Port Display is enabled, CPU use goes straight to 100% and iftop becomes unresponsive. This behavior started sometime in the last few months, and occurs on 2 of the 4 Ubuntu machines that I've tested it on. I compiled iftop 0.17 and 1.0-pre2 from source and observed the same behavior as the precompiled version (1.0-pre2 from the Ubuntu repo) on these computers. I cannot figure out what is unique (other than physical hardware) about the 2 machines that still work, except that they use 3.2 and 3.6 kernels (vs. 3.5 and 3.11 on the machines that don't work). So maybe there's a network driver issue? I checked the version numbers of libc6, libncurses, libpcap, and libtinfo (all the dependencies I know of) and they are the same on 1 of the working machines vs. 1 of the non-working ones. And iftop worked properly on all of these machines until some relatively recent update. So, iftop is completely unusable on at least 2 of my computers. Can anyone recommend further troubleshooting steps that I could take to isolate this problem, preferably without rebooting? Are there any other library versions I should check? Thanks, Alex

2 5

[Iftop-users] Forwarded bug reports from Debian
by Markus Koschany 19 Nov '13

19 Nov '13

Hi all, I am the current maintainer of iftop for Debian GNU/Linux. In the past months and years users reported various bugs and feature requests for iftop and since I don't see that someone forwarded them upstream, I have made a short compilation of those outstanding issues. Feedback is much appreciated. 1. iftop does not notice changes to ppp interfaces and stops refreshing its output http://bugs.debian.org/543138 Iftop does not recognize changes to interfaces. If the interface goes temporarily down and then up again, iftop is not capable of recognizing the change and cannot display the traffic anymore. A manual restart is required to make it work again. It would be nice if iftop could detect such a change and continue with monitoring. 2. iftop: chooses eth0 as the default interface instead of the default route http://bugs.debian.org/644998 If the -i option is not specified, iftop looks for the first interface which is up and falls back to eth0 if none are found. On systems where two interfaces such as eth0 and wlan0 are up and the default route points to wlan0, iftop still chooses eth0 by default. The code could be changed in two ways: * Only consider interfaces with routes associated with them. * Prefer the interface with a default route to other ones. 3. Add a command-line option to specify the Display Mode http://bugs.debian.org/511174 "Currently, the display mode can be toggled between "One line per host", "Received traffic only", "Sent traffic only" and "Two lines per host": - either by pressing the "t" key, - or by setting the "line-display" parameter in the config file. It would be very useful to have a way to specify this through a command-line option, like it's currently possible with most other frequently-used iftop adjustments." 4. Add a "min-bandwidth" option, so less resolution is wasted on logarithmic scale. http://bugs.debian.org/520386 "A "min-bandwidth" option analogous to the "max-bandwidth" option should be added. Currently the logarithmic display wastes a lot of space in the 0 - few-kilobytes-per-second range, which is often not useful (unless you're trying to examine intrusion attempts or something like that), causing the interesting range up to the maximum bandwidth to be crammed into just the right half of the screen. Being able to specify the minimum bandwidth to display would help a lot." 5. NAT support http://bugs.debian.org/631682 One user asked for NAT support for using iftop on a router to monitor traffic. 6. bar graph average should be an option in iftoprc http://bugs.debian.org/704813 The option "bar graph average (-B)" can be used within iftop but there is no corresponding option in iftoprc. Thanks for reading Regards, Markus

3 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

iftop-users November 2013