From: Philip Craig <philipc@snapgear.com>
To: Anton <anton.vazir@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: TC interface
Date: Wed, 27 Feb 2008 18:56:08 +1000 [thread overview]
Message-ID: <47C525A8.1040502@snapgear.com> (raw)
In-Reply-To: <200802271337.31505.anton.vazir@gmail.com>
Anton wrote:
> Looks like everyone is too proud to answer a simple newbee
> question...
More likely busy...
>> I'm trying to figure out how to interface with the
>> kernel's qos structires. I've found libiptc HOWTO - but
>> it's very outdated and provides only IPTABLES
>> manipulation, not traffic scheduler. Could anyone please
>> advice, if there is a C library, which provides an
>> abstraction for easier manipulation with kernel internals
>> to not use "tc" and "iptables"?
This should cover tc:
http://people.suug.ch/~tgr/libnl/
There isn't a C api for iptables other than libiptc, and
it isn't meant to be used outside of iptables anyway.
Also google showed me http://www.coverfire.com/lql/
but I know nothing about it.
next prev parent reply other threads:[~2008-02-27 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 8:58 TC interface Anton
2008-02-27 8:37 ` Anton
2008-02-27 8:56 ` Philip Craig [this message]
2008-02-27 9:12 ` Anton
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=47C525A8.1040502@snapgear.com \
--to=philipc@snapgear.com \
--cc=anton.vazir@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.