netdev - Re: iproute2 action/policer question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Jun 2009 09:09:54 -0400
From:	jamal <hadi@...erus.ca>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	Denys Fedoryschenko <denys@...p.net.lb>,
	Paweł Staszewski <pstaszewski@...are.pl>,
	Linux Network Development list <netdev@...r.kernel.org>,
	Andreas Henriksson <andreas@...al.se>
Subject: Re: iproute2 action/policer question

On Wed, 2009-06-17 at 09:26 +0000, Jarek Poplawski wrote:
> 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).
> > >

Something like that.
It works fine with iptables 1.4.2 for Lenny on my laptop. 
It should work fine for the release after Lenny for 1.4.3 once
the debian maintainers pick up the latest iproute2.
For other Distros: it should work fine if they have iptables 1.4.2/3.
iptables 1.4.4 is not mainstream; i need to add a new test to detect
it once it is mainstream (actually i could do it before it becomes
mainstream and still make it backwards compatible).
I contributed about 10 patches to iptables to try and make sure it
doesnt break again ;-> Hopefully my efforts will be rewarded
(or as the saying goes perhaps "no good deeds go unpunished");->
I have confidence the iptables people are more aware of the API
breakages now than before - so very low probability it will break
post iptables 1.4.4.
For versions lower than iptables 1.4.1 I think i will give up instead of
making it compatible all the way back there.
I use debian exclusively (and these days all my machines are lenny) so
those are the only machines i test on.

> > 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.
> 

It should work with others as well - if it doesnt theres a bug
somewhere. I dont have time this week - but if theres a script that is
supposed to work that doesnt work, please send it to me and i will look
into it.

cheers,
jamal

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html