From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: jamal <hadi@cyberus.ca>,
"Paweł Staszewski" <pstaszewski@itcare.pl>,
"Linux Network Development list" <netdev@vger.kernel.org>,
"Andreas Henriksson" <andreas@fatal.se>
Subject: Re: iproute2 action/policer question
Date: Wed, 17 Jun 2009 09:26:26 +0000 [thread overview]
Message-ID: <20090617092626.GA11005@ff.dom.local> (raw)
In-Reply-To: <200906171201.37727.denys@visp.net.lb>
On Wed, Jun 17, 2009 at 12:01:37PM +0300, Denys Fedoryschenko wrote:
> On Wednesday 17 June 2009 09:28:46 Jarek Poplawski wrote:
>
> > >
> > > I confirm I can't get 'action ipt -j MARK' working on debian lenny
> > > (stable) with distro's iptables/tc. I'm not able to compile tc from
> > > vanilla sources properly either - configure fails 3 IPT tests. (I
> > > admit I can miss setting some (undocumented?) config variables.) So,
> > > with or without debian, IMHO iproute2 needs some updates for iptables
> > > 1.4.2, 1.4.3, and maybe even 1.4.4 now.
> >
> > OOPS! I _can_ configure it for 1.4.2 yet (so it's only about >= 1.4.3).
> >
> I check that, and found again many small changes in iptables, that screwed ipt
> action in iproute2.
>
> I really think it doesn't worth to put too much efforts fixing it, with each
> new release iptables. I switch to other way of "tagging" packets, skbedit,
> and it seems it is also faster.
If it were only about -j MARK you're 100% right. Other targets could
be harder to replace - if they work of course ;-) Of course it's all
up to Jamal, but on the other hand I'm really confused debian stable
(or even testing) maintains such a broken state without any notice
or simply disabling it to save people's time.
Jarek P.
next prev parent reply other threads:[~2009-06-17 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 20:10 iproute2 action/policer question Paweł Staszewski
2009-06-15 11:19 ` Jarek Poplawski
2009-06-15 13:32 ` jamal
2009-06-15 14:52 ` Jarek Poplawski
2009-06-15 16:09 ` Paweł Staszewski
2009-06-15 16:37 ` Jarek Poplawski
2009-06-15 16:44 ` Jarek Poplawski
2009-06-15 17:08 ` Paweł Staszewski
2009-06-15 20:07 ` Jarek Poplawski
2009-06-16 12:04 ` jamal
2009-06-17 6:14 ` Jarek Poplawski
2009-06-17 6:28 ` Jarek Poplawski
2009-06-17 6:45 ` Jarek Poplawski
2009-06-17 9:01 ` Denys Fedoryschenko
2009-06-17 9:26 ` Jarek Poplawski [this message]
2009-06-17 13:09 ` jamal
2009-06-17 13:30 ` Andreas Henriksson
2009-06-17 19:43 ` Jarek Poplawski
2009-06-18 13:19 ` jamal
2009-06-18 18:39 ` Jarek Poplawski
2009-06-15 21:47 ` [PATCH] " Jarek Poplawski
2009-06-16 12:07 ` jamal
2009-06-16 18:33 ` [PATCH v2] " Jarek Poplawski
2009-06-17 9:33 ` Paweł Staszewski
2009-06-18 1:57 ` David Miller
2009-06-15 16:13 ` Paweł Staszewski
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=20090617092626.GA11005@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=andreas@fatal.se \
--cc=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/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.