Thanks for the links, I'm reading it now, but there is a lot of information... My problem is that I don't know how much available bandwidth I have (this is about wireless networks). Otherwise I could just calculate the total throughput on the interface and see if there is some free bandwidth left. Can one with linux traffic control tools or iptables derive the load of interface/queue? The only thing I need to know is whether the output transmission queue can cope with all the traffic waiting for transmission, in other words, is the queue full loaded or not. Thanks, Aleksej. 2008/9/22 paulobruck1 <paulobruck1@xxxxxxxxx>: > Em Seg, 2008-09-22 às 20:25 +0200, Aleksej escreveu: >> Hi, >> > > Hi > >> I know that iptables can be used for some monitoring tasks. Is it >> possible to solve the following task with iptables? >> >> Let's say I have an application that generates 20 Mbps data for >> transmission, but due to high network load only 10Mbps is actually >> transmitted. So, the output transmission queue is always loaded with >> packets waiting for transmission. Is it possible to see somehow with >> iptables that the output transmission queue is always busy? Or maybe >> it is possible to count how many packets were generated for >> transmission and how many packets have been actually transmitted? >> >> I need this for monitoring the queue load. The main task is to monitor >> what portion of time the output transmission queue is empty/busy. >> > Instead of only monitor what about shape/priorize?? see : > > > http://lartc.org/howto > > http://www.linuxfoundation.org/en/Net:IFB > > best regards > > >> Thanks for any hints!! >> >> Aleksej. >> -- >> To unsubscribe from this list: send the line "unsubscribe netfilter" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
