From: jamal <hadi@cyberus.ca>
To: Jens Thiele <karme@berlios.de>
Cc: netdev@vger.kernel.org, linuximq@yahoogroups.com
Subject: Re: traffic shaping with NAT: IFB as IMQ replacement?
Date: Thu, 29 Mar 2007 12:11:56 -0400 [thread overview]
Message-ID: <1175184716.4881.30.camel@localhost> (raw)
In-Reply-To: <m27it09n5w.fsf@quark.karme-net.hirschau>
On Wed, 2007-28-03 at 18:54 +0200, Jens Thiele wrote:
> Hello,
>
> Sorry for the many Ccs, but I hope to reach all parties involved.
> I want to do traffic shaping with NAT and I wanted to do it with IFB
> instead of IMQ [1]. I tried a lot of things but now I am stuck (and
> maybe confused).
>
> The setup:
> eth0 eth1
> WAN/(Internet) <-> Linux Router <-> LAN
>
> Linux router:
> - does NAT for the LANs
> - runs local processes communicating with the WAN/Internet
>
I understand this requirement; unfortunately when i polled for features
majority of people who emailed back were asking for the other things.
I have changed my opinion a little since last time because the
netfilter/contracking code now does netlink. I believe this could all be
achieved in user space. Infact i have started writting some code - the
problem is my time has become intermittent.
If i can get someone who can work with me to complete the work, I will
be more than happy to get that last bastion of IMQ done.
So if you are a fireman willing to be a hero (I guess all firemen want
to be heroes, why else would they be firemen?) email me privately and we
can get this done.
cheers,
jamal
PS:- i have removed lartc from the list because it bounces my emails and
i refuse to subscribe.
next prev parent reply other threads:[~2007-03-29 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 16:54 traffic shaping with NAT: IFB as IMQ replacement? Jens Thiele
2007-03-29 16:11 ` jamal [this message]
2007-03-29 23:08 ` Gerd v. Egidy
2007-03-30 12:33 ` jamal
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=1175184716.4881.30.camel@localhost \
--to=hadi@cyberus.ca \
--cc=karme@berlios.de \
--cc=linuximq@yahoogroups.com \
--cc=netdev@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 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).