From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Writing rules direct to Kernel
Date: Wed, 19 Jan 2005 10:53:57 +0000 [thread overview]
Message-ID: <3063e5050119025336f2dee1@mail.gmail.com> (raw)
In-Reply-To: <1106129520.9814.100.camel@tehnic6.bacau.astral.ro>
I'm intersted too in a program that take an entire qos struncture tree
and filters and put them instantly in kernel, like iptables, i wonder
if there is such project
On Wed, 19 Jan 2005 12:27:40 +0200 (EET), Catalin(ux aka Dino) BOIE
<util@deuroconsult.ro> wrote:
> On Wed, 19 Jan 2005, Liviu Faciu wrote:
>
> > Hi,
> >
> > I'm interested to write rules direct in Kernel space memory and not to
> > execute the tc command. Have anyone done this before ? Any ideas ?
> > Sources ?
> > Thank you,
> > Liviu
>
> Take a look at iproute2 sources. There you have a lib that you can use to
> what you want. Yes, is doable.
>
> >
> >
> >
> > --
> > This message was scanned for spam and viruses by BitDefender.
> > For more information please visit http://linux.bitdefender.com/
> >
> >
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
>
> ---
> Catalin(ux aka Dino) BOIE
> catab at deuroconsult.ro
> http://kernel.umbrella.ro/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-01-19 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 10:12 [LARTC] Writing rules direct to Kernel Liviu Faciu
2005-01-19 10:21 ` Victor Julien
2005-01-19 10:27 ` Catalin(ux aka Dino) BOIE
2005-01-19 10:53 ` George Alexandru Dragoi [this message]
2005-01-19 15:36 ` Liviu Faciu
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=3063e5050119025336f2dee1@mail.gmail.com \
--to=waruiinu@gmail.com \
--cc=lartc@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.