07-18-2006
The best way is to use
pcap library and write small programm (look at
http://www.tcpdump.org/pcap.htm) that monitors all packets which have HTTP header with url of the target site (you can skip parsing all protocols, just look into packet's header for url of the site). But this will not work for SSL
Also try tc (traffic control from iproute2 package). I dont know whether this is appropriate for you but with tc you can create different filters (e.g. according to IP adresses, TCP ports, etc.) and get statistics for that filters, i.e. something similar to
$ tc -s qdisc
qdisc htb 1: dev eth0 r2q 10 default 1 direct_packets_stat 0
Sent 21655 bytes 62 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
A realize that all approaches above are very 'low-level', then just search on sf.net
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm on T1, is there any way i can check my acctual bandwidth?
Thank you all (3 Replies)
Discussion started by: solvman
3 Replies
2. IP Networking
i have two questions actually...
i need to block certain ports with openbsd and PF in a large lan, the firewall is supposed to be a router between the internet and the first lan switch.
first of all, would this work at all in theory?
second, i tried doing this a few days ago at a huge lan but i... (2 Replies)
Discussion started by: nocturnal
2 Replies
3. UNIX for Dummies Questions & Answers
What are my options for monitoring bandwidth on a per user basis? Ideally, I'd like something thats easy to configure (like a webmin module pleeeease?), and that could monitor ALL bandwidth. Not just web bandwidth but also ftp/afp uploading and downloading, and email traffic. I know this is a... (4 Replies)
Discussion started by: l008com
4 Replies
4. UNIX for Advanced & Expert Users
Is there a way to monitor FTP and AFP bandwidth on a per user basis? AFP = AppleFilesharingProtocol, and by monitor, I don't mean graphs, I mean getting raw byte counts I can use in my scripts any way I choose. I am attempting to use mod_watch to monitor virtual domain bandwidth usage, but I really... (0 Replies)
Discussion started by: l008com
0 Replies
5. IP Networking
Hello,
I was wondering how one would go about regulating bandwidth of a server running RH Linux 8.0 and Apache. I am running a webserver, and want only one person to be able to download one file at a time. So, they can't click about 10 files and soak up lots of bandwidth. Plus, I would like to cap... (2 Replies)
Discussion started by: Phobos
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I'm looking for some way to bring up in a shell window a realtime (or something that updates at 10 second intervals or whatever) bandwidth monitor.
I just want something that shows me how much kbps is going in and how much is going out of each interface. Is there something that might... (2 Replies)
Discussion started by: d11wtq
2 Replies
7. IP Networking
Hi,
1-What is bandewidth ?
2-How to calculate ?
3-How to measure ? Any free software to measure it ?
Many thanks. (4 Replies)
Discussion started by: big123456
4 Replies
8. IP Networking
Hi all
I have been running iptraf on a linux box for a few months monitoring bandwidth utilization realtime from mac address with port mirroring.
Now I want to graph these bandwidth utilization. Is MRTG the right software?
Any ideas? (4 Replies)
Discussion started by: palm101
4 Replies
9. Programming
I wish to develop an application to monitor the network traffic of my system.
I wish to know which computer networked to me is using most of the bandwidth. I know the basics of python but do not know how to start the work.. please suggest some good methods to follow. (7 Replies)
Discussion started by: coderhs
7 Replies
LEARN ABOUT CENTOS
tc-codel
CoDel(8) Linux CoDel(8)
NAME
CoDel - Controlled-Delay Active Queue Management algorithm
SYNOPSIS
tc qdisc ... codel [ limit PACKETS ] [ target TIME ] [ interval TIME ] [ ecn | noecn ]
DESCRIPTION
CoDel (pronounced "coddle") is an adaptive "no-knobs" active queue management algorithm (AQM) scheme that was developed to address the
shortcomings of RED and its variants. It was developed with the following goals in mind:
o It should be parameterless.
o It should keep delays low while permitting bursts of traffic.
o It should control delay.
o It should adapt dynamically to changing link rates with no impact on utilization.
o It should be simple and efficient and should scale from simple to complex routers.
ALGORITHM
CoDel comes with three major innovations. Instead of using queue size or queue average, it uses the local minimum queue as a measure of the
standing/persistent queue. Second, it uses a single state-tracking variable of the minimum delay to see where it is relative to the stand-
ing queue delay. Third, instead of measuring queue size in bytes or packets, it is measured in packet-sojourn time in the queue.
CoDel measures the minimum local queue delay (i.e. standing queue delay) and compares it to the value of the given acceptable queue delay
target. As long as the minimum queue delay is less than target or the buffer contains fewer than MTU worth of bytes, packets are not
dropped. Codel enters a dropping mode when the minimum queue delay has exceeded target for a time greater than interval. In this mode,
packets are dropped at different drop times which is set by a control law. The control law ensures that the packet drops cause a linear
change in the throughput. Once the minimum delay goes below target, packets are no longer dropped.
Additional details can be found in the paper cited below.
PARAMETERS
limit
hard limit on the real queue size. When this limit is reached, incoming packets are dropped. If the value is lowered, packets are dropped
so that the new limit is met. Default is 1000 packets.
target
is the acceptable minimum standing/persistent queue delay. This minimum delay is identified by tracking the local minimum queue delay that
packets experience. Default and recommended value is 5ms.
interval
is used to ensure that the measured minimum delay does not become too stale. The minimum delay must be experienced in the last epoch of
length interval. It should be set on the order of the worst-case RTT through the bottleneck to give endpoints sufficient time to react.
Default value is 100ms.
ecn | noecn
can be used to mark packets instead of dropping them. If ecn has been enabled, noecn can be used to turn it off and vice-a-versa. By
default, ecn is turned off.
EXAMPLES
# tc qdisc add dev eth0 root codel
# tc -s qdisc show
qdisc codel 801b: dev eth0 root refcnt 2 limit 1000p target 5.0ms interval 100.0ms
Sent 245801662 bytes 275853 pkt (dropped 0, overlimits 0 requeues 24)
backlog 0b 0p requeues 24
count 0 lastcount 0 ldelay 2us drop_next 0us
maxpacket 7306 ecn_mark 0 drop_overlimit 0
# tc qdisc add dev eth0 root codel limit 100 target 4ms interval 30ms ecn
# tc -s qdisc show
qdisc codel 801c: dev eth0 root refcnt 2 limit 100p target 4.0ms interval 30.0ms ecn
Sent 237573074 bytes 268561 pkt (dropped 0, overlimits 0 requeues 5)
backlog 0b 0p requeues 5
count 0 lastcount 0 ldelay 76us drop_next 0us
maxpacket 2962 ecn_mark 0 drop_overlimit 0
SEE ALSO
tc(8), tc-red(8)
SOURCES
o Kathleen Nichols and Van Jacobson, "Controlling Queue Delay", ACM Queue, http://queue.acm.org/detail.cfm?id=2209336
AUTHORS
CoDel was implemented by Eric Dumazet and David Taht. This manpage was written by Vijay Subramanian. Please reports corrections to the
Linux Networking mailing list <netdev@vger.kernel.org>.
iproute2 23 May 2012 CoDel(8)