From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ Stability
Date: Sun, 25 Jan 2004 03:49:15 +0000 [thread overview]
Message-ID: <007b01c3e2f6$487698f0$030aa8c0@t> (raw)
In-Reply-To: <marc-lartc-105066408632475@msgid-missing>
Internet (eth0) <-> ppp0 ----- ppp1 <-> LAN (eth1) 10.0.0.0/8
this way dont seem excelent because it still lacks some functionality
and what about using LO or dummy type interface instead of ppp?
the new imq driver that i am developing will have unlimited posibilities
it willbe fake interface wich passes all ip trafic without exception no
mater which direction, destination and so on
even localy generated and received trafic should pass it
I removed iptables module so noo need to configure it just everything is
catched.
so you will be able to shape in + out in one
also I am thinking about the chaining functionality
is there any need to make chain of imq devices ? ( they will get the all
same trafic)
you will be able to use few shapers then but it will add latency.
I almost finished my driver , but unfortunately there is no way to avoid
patching kernel.
I need to export ip_finish_output2 and ip_local_deliver_finish functions but
dont know how to do that, and where is the best place.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-25 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 11:28 [LARTC] IMQ Stability hare ram
2004-01-23 17:29 ` Michael S. Kazmier
2004-01-24 23:24 ` Roy
2004-01-24 23:38 ` mkazmier
2004-01-25 2:04 ` Alexander Clouter
2004-01-25 3:49 ` Roy [this message]
2004-01-25 8:56 ` Aron Brand
2004-01-26 10:36 ` Remus
2004-01-26 15:53 ` Michael S. Kazmier
2004-01-26 18:49 ` rubens
2004-01-27 0:39 ` Alexander Clouter
2004-01-28 8:25 ` Alexander Trotsai
2004-05-26 23:56 ` [LARTC] IMQ stability Damion de Soto
2004-05-28 22:21 ` Andre Correa
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='007b01c3e2f6$487698f0$030aa8c0@t' \
--to=roy@xxx.lt \
--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.