Hello Lesha! :p Thank you very much! I actually found the TC sources (not lib nor api, but sources) in the iproute package (tc.c, tc_qdisc.c, tc_class.c etc) and they seem to be somewhat straight forward. But I'll check the lgl lib as well! Maybe it's easier than the tc sources.. Thanks again :) > Hello Katia! > > There is a library lql ( http://www.coverfire.com/lql/) for working with > linux QoS It's GPL. > I don't know the state of this library. > > TC doesnt' use it, the TC's approach is directly communicate with kernel > via netlink. > > On 10/09/2012 09:23 PM, Katia S. wrote: >> Yeah, that's why I installed the development packages of both iptables >> and >> iptc. I'm gussing the API I need is in the iptc lib.. But still, no luck >> finding a tutorial there either. >> >> And I guess the Title of this mail is kinda wrong and slighty irrelevant >> :p >> Sorry 'bout that.. >> >> Do you have any suggestions regarding the iptc API and maybe any source >> code samples (aside the ones that are already installed inside the core, >> of course :p ) ? >> >> >>> On Tuesday 2012-10-09 17:33, Katia S. wrote: >>> >>>> Well, I have been running "tc" commands like "tc qdisc" or "tc class" >>>> to >>>> get some information I need on various devices and interfaces. >>>> >>>> Right now I need to implement the exact same feature in a program of >>>> mine, >>>> but I don't want to just externally call the "tc" command and read its >>>> output... So I was searching for an API to use it in my source code. >>>> My >>>> search led me to the iptc-dev and iptables-dev libraries, but those >>>> have >>>> no tutorial or how-tos so I'm kinda lost... >>> tc is not part of iptables, so it is very unlikely (I say impossible) >>> that iptables-dev will get you anything tc-related. >>> >> > > > -- > Best regards, > Alexey Perevalov, > -- Katia Sarsempagieva Research Associate Media Networks Laboratory Institute of Networks and Telecommunications NCSR "Demokritos" -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
