From: "Katia S." <katias@iit.demokritos.gr>
To: "Jan Engelhardt" <jengelh@inai.de>
Cc: "Katia S." <katias@iit.demokritos.gr>,
"Maciej Żenczykowski" <zenczykowski@gmail.com>,
netfilter-devel@vger.kernel.org,
"Pablo Neira Ayuso" <pablo@netfilter.org>
Subject: Re: iptables-dev Source Example
Date: Tue, 9 Oct 2012 20:23:09 +0300 (EEST) [thread overview]
Message-ID: <11f6603b92965503cfaef2622aaf56a0.squirrel@webmail.iit.demokritos.gr> (raw)
In-Reply-To: <alpine.LNX.2.01.1210091753520.12373@nerf07.vanv.qr>
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.
>
--
Katia Sarsempagieva
-----
Research Associate
Media Networks Laboratory
Institute of Networks and Telecommunications
NCSR Demokritos
next prev parent reply other threads:[~2012-10-09 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 13:36 iptables-dev Source Example Katia Sarsempagieva
2012-10-08 15:22 ` Pablo Neira Ayuso
2012-10-08 18:42 ` Maciej Żenczykowski
2012-10-09 15:33 ` Katia S.
2012-10-09 15:55 ` Jan Engelhardt
2012-10-09 17:23 ` Katia S. [this message]
2012-10-09 22:08 ` Jan Engelhardt
[not found] ` <5076A36D.8020505@samsung.com>
2012-10-11 10:49 ` Katia S.
2012-10-09 15:05 ` Giuseppe Longo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11f6603b92965503cfaef2622aaf56a0.squirrel@webmail.iit.demokritos.gr \
--to=katias@iit.demokritos.gr \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zenczykowski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).